delete_qrcode

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

Discloses the side effect of deleting the underlying file, which is beyond the basic operation. However, no permissions, irreversibility, or error conditions are mentioned. With no annotations, more detail would be beneficial.

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?

Extremely concise, one sentence front-loaded with the verb. Every word adds value, but the lack of parameter guidance slightly reduces effectiveness.

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 the output schema existing, the description does not explain what the tool returns upon success or failure. It also fails to cover error cases or any constraints, leaving the agent potentially uncertain about outcomes.

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 description coverage is 0%, and the description provides no explanation of the 'id' parameter. The agent has no additional context about what 'id' refers to or its format.

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?

Description clearly states the action ('delete') and the resource ('QR code'), and adds the detail about deleting the underlying file if any. This distinguishes it from sibling tools like 'remove_qrcode_logo' or 'replace_qrcode_file'.

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 vs alternatives, no prerequisites, and no mention of limitations or when not to use. Only implicit that you use it to delete a QR code.

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