delete_email_number_address_url_email_id

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

No annotations provided, so the description carries full burden. It lists error codes (`noent`, `exists`, `no_match`) which gives some insight into failure modes, but does not disclose side effects, reversibility, permissions, or whether the operation is idempotent. The behavioral disclosure 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?

Two sentences: one for the action, one for error codes. Extremely concise, front-loaded with the primary purpose, and no unnecessary words.

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?

Despite having an output schema (per context), the description does not explain the return value. The parameter semantics are missing, and there is no mention of prerequisites or typical use. For a simple delete tool, it is still incomplete without clarifying what the id refers to and what the output schema contains.

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 description coverage is 0%. The description only says 'the given id' for the parameter, which adds no meaning beyond the schema's property name. It does not explain what the id represents, any format constraints, or how to obtain it.

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, which is a specific and actionable verb+resource. However, given the sibling tools like delete_address_number_address_url_email_id and delete_number_number_address_url_email_id, the description does not differentiate why one would use this tool over those, making it slightly vague in context.

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 compared to alternatives. The error codes are listed but no context about prerequisites, typical use cases, or conditions where this tool is appropriate versus other delete tools for similar entities.

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