delete_qrcode

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

Discloses the effect that scanning the deleted QR code will no longer open the ordering page. However, with no annotations, the description carries full burden; it lacks details on irreversibility, permission requirements, or side effects on related entities.

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 sentences, front-loaded with action and consequence. Every word is informative. No redundancy.

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 tool with one parameter and no output schema, the description covers the core functionality and outcome. However, it lacks usage guidance and behavioral details that would make it self-contained.

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?

Single parameter 'id' is well-documented in the schema ("QR code ID to delete"). Description adds minimal extra meaning ("by ID"). Schema coverage is 100%, so 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?

Clear verb "Delete" and resource "QR code by ID". Explicitly states the consequence (scanning no longer opens ordering page). Distinguishes from sibling tools like create_qrcode, update_qrcode, get_qrcode.

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?

No guidance on when to use this tool versus alternative deletion tools (e.g., bulk_delete_locations). No mention of prerequisites or conditions for safe deletion.

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