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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that deletion is permanent and cannot be undone, requires authentication, prevents accidental/injected deletions via title matching, and refuses mismatches. This is strong transparency, though it doesn't mention return behavior or side effects beyond scan history deletion.

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 slightly lengthy (5 sentences) but every sentence contributes essential safety and workflow information. It is front-loaded with the primary purpose and then systematically explains prerequisites and failure conditions.

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?

Despite no output schema, the description covers all necessary context for a destructive tool: the action, irreversibility, required confirmation step, and authentication. The workflow is fully specified, leaving little room for misuse.

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% with detailed descriptions for each parameter. The description adds critical semantics for confirm_title, explaining that it must match exactly and why, plus when to supply qr_code_id vs short_code. This exceeds the baseline of 3.

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 ('delete') and resource ('QR code and its scan history'), clearly distinguishing it from sibling tools like create_qr_code and update_qr_target. It also conveys the permanence of the action.

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 gives clear context on when to use the tool and explicitly instructs to call get_qr_code or list_qr_codes first to retrieve the exact title. It lacks explicit exclusions (e.g., 'use update_qr_target for modifications') but provides sufficient guidance for correct usage.

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