tool_qrcode

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

No annotations are present, and the description offers minimal behavioral context. It lists outputs (image, dataUri) but does not explain side effects, required permissions, or the behavior of error correction or color handling. The description does not contradict annotations but fails to disclose meaningful behavior.

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 concise but is essentially a structured list that repeats the schema. It lacks a prose explanation that front-loads the tool's purpose. It is not verbose, but it is under-specified.

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 QR code generation tool with no annotations and no output schema, the description is incomplete. It does not state which parameters are required, default values, or how the output image is returned. The confusion from the schema's inclusion of output properties as inputs is only partially resolved.

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 schema contains descriptions for all parameters, but they are just property names (e.g., 'Data', 'Size'). The description repeats these without adding details like valid error correction levels, color format, or units. It does, however, clarify that 'image' and 'dataUri' are outputs, which helps disambiguate from the schema's inclusion of them as properties.

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 is 'QRCode' with a parameter list. It lacks an explicit verb like 'Generate' or 'Create', so it does not clearly state what the tool does. The resource is identified but the action is implied, and it does not distinguish itself from sibling tool tool_qrcode_decode.

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 provides no guidance on when to use this tool or when to prefer alternatives. It does not mention prerequisites, exclusions, or comparison to decode or other image tools.

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