delete-route

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

The annotation destructiveHint: true already indicates the destructive nature, and the description's 'Delete' is consistent. However, the description adds no extra behavioral details beyond the annotation, such as irreversibility or side effects.

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 a single sentence, very concise and front-loaded. However, it could be slightly more informative without losing conciseness.

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 tool with only one parameter and no output schema, the description is too minimal. It doesn't explain the effect on the deployed service, whether it's reversible, or how to obtain the route ID.

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?

With 100% schema description coverage, the description adds no extra meaning to the route_id parameter beyond what the schema already provides ('The route ID'). No format or examples are given.

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 public route or custom domain mapping, using the verb 'delete' and specifying the resource. However, the typo 'Bult' instead of 'built' slightly reduces clarity. It distinguishes from sibling tools like create-route or update-route.

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 gives minimal usage context, only stating the action. It does not specify when to use this tool versus alternatives like update-route or delete-service, nor does it mention prerequisites or consequences like service impact.

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