Delete a route

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the bar is lower; the description adds the non-obvious fact that nothing is sent unless confirm: true and that there is no server-side dry run, a meaningful constraint not present in the annotations. It stops short of saying whether deletion is recoverable or what happens to routes referenced by existing deliveries.

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 short sentences, action and endpoint front-loaded, then the write gate. No filler, no repetition.

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 destructive, open-world delete with no output schema, the definition covers the safety gate but not the blast radius: no mention of whether deletion is permanent, whether in-flight deliveries or references are affected, or what the returned preview contains. Adequate to call correctly, insufficient to call confidently.

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 67% and the confirm and idempotencyKey parameters are already documented in the schema, including the preview behavior. The description adds only the qualifier 'no server-side dry run' on top of that, while the required id parameter remains undocumented in both places.

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?

Specific verb plus resource ('Delete a route') anchored by the HTTP endpoint DELETE /v1/notification-routes/{id}, which lets an agent distinguish it from notifications_deleteChannel and notifications_listRoutes without opening the schema. No explicit sibling naming, but the resource is unambiguous.

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 delete a route versus updating or disabling it, no prerequisite (e.g. list routes first), and no statement about permanence or effect on pending deliveries. Only the confirm gate is mentioned, which is invocation mechanics rather than tool selection guidance.

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