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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely new consequence information beyond that: deletion is permanent and redirects cease immediately, which tells the agent the blast radius before calling. It stops short of covering error behavior for unknown codes or whether click stats are retained.

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?

Two short sentences with no filler; the permanence warning is front-loaded and the operational consequence follows immediately. Nothing could be removed without losing meaning.

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 one-parameter destructive tool with full annotation coverage, the definition supplies what an agent needs to decide and act. The only gap is return/error behavior (no output schema exists and the description says nothing about a not-found response), which is minor at this complexity.

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?

There is a single parameter, short_code, already fully documented in the schema (100% coverage), so the schema carries the burden. The description adds no format, length, or lookup semantics for the code, leaving it at the baseline for a fully-described single-parameter tool.

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 ('Permanently delete') and resource ('a short link'), which cleanly separates it from sibling tools like update_link, get_link, and the other delete_* tools that target domains, folders, or webhooks.

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 implies the tool is for removing a link for good, but it never states when to choose it over alternatives such as update_link (e.g., disabling a link instead of deleting it) or what happens if the code does not exist. Usage is inferable but not guided.

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