delete_short_url_visits

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

Adds valuable behavioral context beyond the annotations: 'permanently erase' signals irreversibility, and the requirement for an environment variable and confirmation parameter is disclosed. This is consistent with the destructiveHint and idempotentHint annotations.

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?

A single, front-loaded sentence conveys the purpose and key prerequisites with zero waste.

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 simple destructive tool with annotations and schema, the description covers the essential aspects: purpose, prerequisite, and permanence. It could mention failure behavior when conditions are unmet, but this is not required given the annotations.

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 already describes shortCode and domain, and confirm is constrained to true. The description only reiterates confirm=true without adding new parameter semantics. With 67% schema coverage, the description adds little beyond the schema.

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 states a specific verb ('erase') and a specific resource ('visit history for one short URL'), clearly distinguishing it from sibling tools like delete_short_url (deletes the short URL itself) and delete_orphan_visits (deletes orphan visits).

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?

Clear context is provided by indicating the destructive nature and the required prerequisites (SHLINK_ALLOW_DESTRUCTIVE=true and confirm=true). However, it does not explicitly name alternatives or when not to use this tool, so it stops short of full guidance.

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