startPhoneVerificationSend a verification code to a phone number to confirm ownership and validate identity before proceeding with account or deployment actions.
Send a verification code to a phone number
| Name | Required | Description | Default |
|---|---|---|---|
| requestBody | No | The JSON request body. |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations include 'destructiveHint: true', the description does not elaborate on side effects such as sending an SMS, potential costs, or rate limits. It only states the action without disclosing any behavioral nuances beyond the annotation.
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?
The description is a single, concise sentence with no filler or redundant information, achieving high clarity with minimal text.
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 simple tool, the description covers the core action, but lacks details on phone number formatting or what the response will be. Given the absence of an output schema, this gap is notable but not critical for basic usage.
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?
The schema only provides a 'phone' string with length constraints, but no description of format (e.g., E.164, country code). The tool description does not supplement this, leaving the parameter's expected format and semantics unclear.
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 clearly states the action ('Send a verification code') and the target ('a phone number'), making the purpose unambiguous. It distinguishes from the sibling 'verifyPhone' by implying the start of the process rather than verification itself.
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?
The description provides no guidance on when to use this tool versus alternatives such as 'verifyPhone'. It does not mention prerequisites, expected outcomes, or any conditions that would make this tool the appropriate choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.