delete_url_number_address_url_email_id

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

The description mentions error codes but lacks detail on side effects, permanence, or authorization requirements. With no annotations, the description carries the full burden but only provides minimal behavioral insight.

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 concise, consisting of one sentence and error codes. It is front-loaded and efficient, though it lacks any structural elements like sections.

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 tool, the description provides minimal context. It does not explain what a ContactNumber is, nor does it mention related resources or operations. The error codes are useful but insufficient.

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 description merely restates that an 'id' is used, adding no meaning beyond the input schema. With 0% schema description coverage, this is a significant gap.

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 deletes a ContactNumber by id, using a specific verb and resource. However, it does not differentiate from sibling tools that also delete other contact-related items, which could cause confusion.

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 alternative delete tools (e.g., delete_address..., delete_email..., etc.). The agent is left to infer from the resource name.

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