misc_qrcode

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add value by revealing that png format returns a base64 dataURL and that output_path can save a file, plus clarifying error_level values. However, it does not mention default size/margin behavior, return format for svg, or error/edge-case handling.

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 a single dense sentence that front-loads the primary action and then efficiently lists the most important optional parameters. Every phrase adds value, with no wasted words.

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 generation tool with no output schema and no annotations, the description covers the core parameters and return type, but omits size and margin defaults, exact output structure, and any usage examples. It is adequate for basic selection but incomplete for fully autonomous invocation without relying on parameter names.

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 low (33%), so the description must compensate. It adds meaning for format (png/svg, dataURL), error_level (L/M/Q/H), and output_path (save file), which are otherwise undocumented in the schema. However, the size parameter remains completely unexplained, and the description does not clarify margin or text beyond the schema.

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 clearly states the tool's purpose: "二维码生成" (QR code generation), with a specific verb and resource. It mentions key format options, but does not explicitly differentiate from sibling tools like misc_barcode, though the name itself distinguishes them.

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 is given on when to use this tool versus alternatives. The description only lists configuration options, not usage context or exclusions. There is no mention of scenarios where QR code generation is appropriate or alternatives like barcode generation.

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