Where the workflow shifted
Vercel AI SDK tool-calling docs focus on schemas, parameters, and execution results; product pages need to turn those constraints into reader-selectable jobs.
Write parameters as business inputs: store, country, SKU, budget, channel, approver, and delivery format instead of exposing raw API fields first.
Tool names are not outcomes
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check permissions and failure
- Use a business-input template to inspect `ai-vertical-services-en` resource cards
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Showing technical parameters too early loses non-developer readers; hiding business inputs slows developer adoption. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.