delete_number_number_address_url_email_id

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

The description lists error codes (noent, exists, no_match) which hint at failure conditions, but with no annotations, it fails to disclose side effects, idempotency, or authorization requirements. The behavioral detail is minimal.

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 extremely concise with two sentences: one stating the action and resource, the other listing error codes. Every sentence adds value with no redundancy.

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 lack of annotations and output schema visibility, the description omits important context like idempotency, required permissions, and response details. The error codes partially compensate but overall completeness is low.

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 has 0% parameter description coverage, and the description does not elaborate on the 'id' parameter's format, constraints, or meaning beyond being an identifier. No added value over 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 the tool deletes a ContactNumber using an id, distinguishing it from sibling tools like delete_address_number_address_url_email_id which delete addresses, emails, or URLs.

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 is provided on when to use this tool versus alternatives such as delete_email_number_address_url_email_id or get_number_number_address_url_email_id. The description lacks context for selection.

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