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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the downstream consequence that already-printed copies stop working, telling the agent this is a materially destructive act. It still omits reversibility/permanence and any auth requirements, so not a 5.

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?

Two short sentences with zero filler, front-loading the action and then the consequence. Optimal size for a one-parameter operation.

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 delete with one parameter, no output schema, and annotations carrying the safety profile, the description is close to complete: what it does plus the key user-facing consequence. The unaddressed 'id' semantics keep it from being fully 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 single required 'id' parameter has 0% schema description coverage, so the schema does not explain it and the description never mentions it either. The agent is left to guess what identifier is expected (QR code UUID vs short code) and where to obtain it. The description fails to compensate for the coverage gap.

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 ('Delete') and resource ('QR code'), immediately distinguishing it from sibling qrs_create, qrs_update, and the deletes for other resources (designs_delete, templates_delete). An agent can identify the correct tool from the phrase alone.

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?

Usage is implied by the verb and resource, but there is no explicit when-to-use/when-not guidance, no mention of how this differs from destructive siblings, and no prerequisite information. It is adequate for such a simple, obvious operation but adds no routing help.

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