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

Annotations already flag destructiveHint=true, but the description adds the critical guard behavior: unnarrowed deletes are blocked unless confirmDeleteAll is passed, and deletions are permanent. This is genuine behavioral context beyond the annotation.

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?

Three sentences, all load-bearing: purpose, narrowing + guard, and the preview recommendation. The destructive scope is front-loaded.

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?

An output schema exists, so return values need not be explained. For a destructive, no-required-param tool, the description covers everything an agent needs to call it safely.

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 schema baseline is 3, but the description adds the interplay between filters and confirmDeleteAll (that the flag is required precisely when no filter is supplied) and explains the A/B pair as source/target property narrowing.

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 opens with a specific verb+resource ("Permanently deletes saved redirect mappings") and its scope is unmistakable. It is clearly distinguishable from the sibling add_migration_redirects and from the read-only list_migration_redirects.

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?

It states exactly when to narrow (label and/or A/B property pair), when confirmDeleteAll: true is mandatory, and why (an unnarrowed delete would also wipe unrelated migrations). It also routes the agent to list_migration_redirects with the same filters as a preview step.

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