delete_address_number_address_url_email_id

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

No annotations provided. The description only lists error codes ('noent', 'exists', 'no_match') but does not disclose side effects, permissions, reversibility, or rate limits. Minimal transparency beyond error handling.

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 fluff. First sentence states purpose, second lists error codes. Efficient but could benefit from slight restructuring for readability.

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 delete operation with one parameter and an output schema, the description misses critical details about parameter usage and behavioral implications. Error codes help but are insufficient for complete context.

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 has one parameter (id) with no description. The description does not elaborate on the parameter's format, type, or meaning. Schema coverage is 0%, and the description fails to compensate.

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 states 'Deletes the ContactNumber with the given id,' clearly specifying the verb and resource. However, the tool name is misleading (address_number_address_url_email_id vs ContactNumber), which could cause confusion. It distinguishes from other delete tools by naming the specific resource.

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 alternatives. No context about prerequisites or exclusions. The description simply states the function, leaving the agent without decision-making support.

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