misc_barcode

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

With no annotations, the description carries the full burden. It adds useful context such as 'png（base64）或 svg' and 'output_path 可保存文件', indicating return format and file-saving side effect. However, it omits behavioral constraints like barcode type-specific text requirements (e.g., EAN-13 must be 13 digits) and does not fully describe the output when output_path is absent.

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, front-loaded sentence that starts with the core purpose and efficiently packs in key options for type, format, and output_path. There is no waste or 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?

The tool is relatively simple, but the description is incomplete for a tool without annotations or output schema. It misses important constraints (e.g., text format requirements for specific barcode types) and does not clarify the exact return value when output_path is not provided. Still, it covers the main functionality and key options, making it minimally viable.

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 coverage is only 20% (only text has a description). The description adds meaning for format (png is base64) and output_path (can save file), which is valuable. However, it merely repeats the enum options for type without adding deeper meaning, and does not mention height at all. It partially compensates for low schema coverage but not fully.

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 as '条形码生成' (barcode generation), which is a specific verb+resource. It also lists the supported barcode types and output formats, distinguishing it from sibling tools like misc_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?

The description implies usage for barcode generation but does not explicitly state when to use this tool over alternatives or provide any exclusions. It lacks guidance on when not to use it, though the clear purpose makes intended usage obvious.

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