delete_an_address

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

Annotations already provide destructiveHint=true and readOnlyHint=false, which are reinforced by the description's 'DESTRUCTIVE' label. The description adds the HTTP method (DELETE) and path, plus the confirmation requirement. No contradictions with 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?

The description is short and includes key elements: destructive hint, resource, HTTP method, and confirmation advice. It is front-loaded with the warning. Could be slightly more concise by removing the URL duplication, but overall efficient.

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 the simplicity of the tool (single parameter, no output schema, and annotations clarifying safety), the description provides sufficient context. It covers the main concern (destructiveness and confirmation) and matches the tool's actual behavior.

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 coverage for the single parameter (id) is 100%, so description does not need to add much. The description mentions the id parameter implicitly via the URL path '/addresses/{id}', but does not explain it beyond what the schema says ('ID of the Address to delete'). Baseline score of 3 is appropriate.

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 ('Delete an address') and the resource ('Addresses'). It uses the verb 'delete' and specifies the resource, making it easy to distinguish from sibling tools like create_an_address or update_an_address.

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 includes a clear directive: 'Confirm with the user before calling.' This guides the agent on when to use the tool (after confirmation). It implicitly indicates this is for deleting addresses, but does not explicitly contrast with other tools. However, the sibling list includes many delete tools, so the specific resource helps.

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