delete_short_url

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable context by emphasizing the permanent nature of the deletion and explicitly requiring an environment variable and confirm flag. This goes beyond the annotations and helps the agent understand the irreversible impact and safety prerequisites.

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 two short, direct sentences. It front-loads the main action ('Permanently delete a short URL') and immediately provides prerequisites. No unnecessary words or repetition of schema details.

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 destructive operation with no output schema, the description covers the essential aspects: what it does, prerequisites, and the permanent nature. It could be more complete by mentioning that it deletes the URL itself (not associated visits), but the tool name and sibling context make this inferable. Overall, it is sufficient.

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 schema already describes shortCode and domain, covering 67% of parameters. The description adds meaning to the confirm parameter by stating 'confirm=true,' which is not described in the schema. This clarifies that the parameter must be true, filling a gap in 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 the action: 'Permanently delete a short URL.' This uses a specific verb and resource, and the word 'permanently' distinguishes it from non-destructive operations. It also differentiates from sibling tools like delete_short_url_visits, which target visits rather than the URL itself.

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 clear prerequisites for usage: it requires SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true. This gives context on when the tool can be invoked. However, it doesn't explicitly mention alternatives or exclusion criteria, such as 'for deleting visits, use delete_short_url_visits,' so it falls short of a 5.

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