deleteRedirect

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

Annotations already indicate destructiveHint:true and idempotentHint:true. The description adds that deletion is permanent, cannot be undone, with no soft-delete via API, and specifies the return message. This adds useful behavioral context beyond annotations, though it could mention error handling for non-existent IDs.

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 concise and well-structured with clear sections (use when, required, see also, destructive, returns). Every sentence adds value, and the structure makes it easy to parse.

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 simplicity of the tool (single parameter, no output schema), the description is complete. It covers purpose, usage guidance, parameter requirement, behavioral impact, return value, and references a sibling tool. No critical information is missing.

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?

The input schema has 100% coverage with a description for redirect_id. The description merely reiterates that redirect_id is required, without adding new semantic meaning. Baseline of 3 is appropriate given high schema coverage.

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 that the tool deletes a redirect permanently, specifying the resource (redirect record) and action (delete by ID). It distinguishes itself from siblings like updateRedirect by noting that updateRedirect modifies without removing.

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 explicit when-to-use scenarios (old redirect no longer needed, conflicting rule) and points to an alternative tool (updateRedirect). It also advises confirming with the user before bulk use, which is excellent guidance.

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