delete_customer_address

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

With no annotations, the description must carry full transparency weight. It only states the destructive action ('Delete') without disclosing consequences like irreversibility, permission requirements, or error behavior. Minimal value beyond the tool name.

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?

Single sentence, front-loaded, no extraneous wording. For a simple delete operation, this is appropriately concise and well-structured.

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 tool's low complexity and complete schema, the description is minimally viable. However, it lacks any mention of return values, side effects, or prerequisites, which would enhance completeness even for a simple delete.

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?

Input schema provides 100% coverage of both parameters (customerId and addressId) with descriptions. The tool description adds no extra parameter meaning, justifying the baseline score of 3.

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?

Description clearly states a specific verb ('Delete') and resource ('a customer's address'), distinguishing it from sibling tools like create_customer_address and update_customer_address. No ambiguity about what action is performed.

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 provided on when to use this tool versus alternatives (e.g., when to update instead of delete, or prerequisites like address existence). The description gives no context for decision-making.

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