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

Annotations already mark destructiveHint and readOnlyHint, but the description adds valuable behavioral context: the deletion is a move to trash, scoped to the active account, and reversible from the web app. This goes beyond the annotations and clarifies the nature of the destructive action.

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?

Every sentence carries meaningful information: the operation, the usage condition, reversibility, and a caution about resolving the identifier. It is compact, direct, and well-structured with the main purpose 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?

For a single-parameter destructive tool with rich annotations and an output schema, the description provides complete guidance: what happens, when to use it, why it is safe, and how to handle ambiguity. Nothing essential is missing.

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 qr_id as a stable identifier and has 100% coverage. The description reinforces the need to resolve ambiguity but does not add new parameter-level detail, so the baseline of 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?

The description clearly states a specific action — moving a QRCodeKIT link and its QR code to the active account's trash. It disambiguates deletion from other operations and is distinct from sibling tools, which are largely create/list/stat tools.

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?

Explicitly states when to use: 'Use this only when the user asks to delete, remove, or discard a specific link.' It also advises resolving the exact qr_id first when the target is ambiguous, giving practical decision guidance.

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