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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false. The description adds valuable context beyond annotations: irreversibility, that statistics are also deleted, that links become error pages, that Cuttly cannot restore, no retry behavior, and plan requirement. Strong addition.

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?

Front-loads the critical warning (WRITE, IRREVERSIBLE) and is reasonably concise. The raw API URL at the end is somewhat extraneous for an agent but not harmful.

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?

Complete for a destructive one-parameter tool: covers irreversibility, confirmation requirement, plan gating, and retry semantics. No output schema exists but none is needed given the irreversible delete nature.

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 fully documents the single 'link' parameter with example. The description does not add format details beyond what the schema provides. 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?

States a specific verb+resource (permanently delete a short link and its statistics) and specifes the blast radius. Clearly distinct from siblings like update_link or set_link_expiration.

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?

Gives clear context: requires user confirmation of the exact link, and needs the Single plan or higher. Does not name alternatives (e.g., update_link to disable instead of delete), but provides strong preconditions.

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