Delete redirect/rewrite rule

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

Annotations already declare destructiveHint=true and idempotentHint=true, which the description reinforces by stating 'Delete'. The description also adds transparency by revealing the exact API endpoint called (DELETE /services/{serviceId}/routes/{routeId}). No contradictions with annotations.

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 (two sentences), but the first sentence ('Delete redirect/rewrite rule') is redundant with the title. It earns its place by adding the second sentence about the API call, though overall structure is efficient but slightly repetitive.

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 operation with two parameters, the description covers the action and the API endpoint. Annotations fill in idempotency and destructiveness. No output schema is needed. However, it does not mention prerequisites (e.g., route must exist) or error handling. Still, it is largely complete given the tool's simplicity.

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?

Both parameters (routeId, serviceId) are 100% covered in the input schema with descriptive names and descriptions. The description's mention of 'a particular redirect/rewrite rule for a particular service' adds minimal semantic value beyond the schema. Schema coverage is high, so baseline 3 is appropriate.

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?

Title and description clearly state the tool deletes a redirect/rewrite rule. The specific verb 'Delete' and resource 'redirect/rewrite rule' are used, and the description distinguishes from sibling tools like render_add_route and render_put_routes by focusing exclusively on deletion.

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 specifies the tool is used to delete a particular route for a particular service, which implies the context of use. However, it does not provide when-not-to-use guidance or mention alternatives (e.g., use render_patch_route for updates or render_disable_route). No explicit exclusion criteria.

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