Delete a routing object

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

The description merely restates the critical hint provided in the annotations ('Destructive'). It does not add any unique behavioral context, such as specific failure modes, permissions required, or side effects beyond the deletion itself, which a mutation tool should detail.

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 definition is maximally concise, delivering the core action, resource, and impact (destructive) in a single, highly readable sentence that is front-loaded with the most critical information.

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 100% schema coverage and strong annotations, the description is sufficient for identifying the tool. However, its brevity prevents it from providing a complete picture of the process or required operational context for the agent.

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 coverage is 100%, so the structure is well-defined. The description mentions 'number_or_id,' which is already explicit in the schema, thus providing only baseline value without adding deeper semantic meaning to the parameter's function.

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 verb ('Delete') and the resource ('routing object'). It further enhances clarity by including the specific HTTP method and endpoint structure (DELETE /routings/{number_or_id}), which distinguishes it from general routing tools.

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?

The description provides almost no guidance on when or why this tool should be used. While it labels the action as 'Destructive,' it fails to explain operational context or when it is necessary compared to other potential routing management tools.

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