Update the phone

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

No annotations provided. Description does not disclose behavioral traits such as whether it overwrites the existing phone, requires specific permissions, or any side effects. The verb 'update' implies mutation, but no additional context is given.

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 very short and includes the HTTP method and tags, which is useful but not structured optimally. It lacks critical information about request structure and constraints.

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?

Given no output schema, no annotations, and nested required parameters, the description is incomplete. It fails to explain how to construct the request (e.g., that path and body are required) or what the response looks like.

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 description coverage is 0%. The description does not explain any parameters; it only mentions 'Body: application/json'. The agent must infer from the schema that 'path' requires contactsId and phoneId, and 'body' requires a phone string. This adds little value 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 clearly states it updates a phone and includes the endpoint path, which specifies it's for a contact's phone. It distinguishes from create/delete siblings by using 'update'. However, it does not explicitly state that it updates the phone number specifically, leaving slight ambiguity.

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 create, delete, or other update tools. It does not mention prerequisites or contextual clues for when to invoke this tool over alternatives.

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