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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds real value beyond them by disclosing the downstream consequence: printed copies of a deleted dynamic code stop working. It stops short of stating permanence or what happens to historical stats.

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?

Three short sentences, zero filler, with the operation stated first and the consequence and confirmation warning following in priority order. Nothing could be removed without losing information.

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 mutation with full annotation coverage and no output schema, the description covers the action, the visible consequence, and the confirmation requirement. It is only slightly short of complete in not stating whether deletion is reversible or what happens to associated stats.

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% and the single qrId parameter is already documented as coming from list_qr_codes or create_qr_code. The description adds nothing about the identifier, which is acceptable given the schema does the work, so the baseline of 3 applies.

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 and resource ("Delete a QR code") that matches the title and leaves no ambiguity about the operation. It does not, however, distinguish itself from siblings like update_qr_code or explain what deletion means relative to those alternatives.

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 instruction "Confirm with the user first" gives a concrete prerequisite for invoking it, which is more than most mutation tools offer. But there is no guidance on when to prefer deletion over, say, deactivating via update_qr_code, and no stated exclusions.

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