Provision Vapi client

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint, destructiveHint=false, and openWorldHint. The description adds context by stating 'Reuses an existing local record by default', which clarifies the idempotent behavior, and 'secret-free' adds a security attribute. No contradiction with annotations, and it enriches the agent's mental model beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The primary action is front-loaded, and the 'reuse' behavior is stated succinctly. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 parameters and no output schema, the description is brief. It does not explain return values, error scenarios, or how this step fits with sibling tools like attach_phone or set_prompt_and_voice. The scope of 'provision' relative to those separate setup steps is ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 70% of parameters with descriptions. The description refers to the 'inbound answering template', aligning with templateId's default, but does not add syntax or details for the remaining parameters (e.g., crm, webhookUrl, transferNumber). It offers minimal supplementary meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Create') and specific resources (client's Vapi assistant, local client record) and mentions the source template. It is distinct from a generic 'process' but does not explicitly differentiate from the sibling apply_template, which may also involve templates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like apply_template, attach_phone, or set_prompt_and_voice. The note 'Reuses an existing local record by default' is an implementation detail, not a usage directive. No exclusions or alternative routes are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.