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

The description adds meaningful behavioral context beyond the neutral annotations: every row returns as its own download link valid for one hour, and the tool is Pro-only while the free tier is limited to one code per call. This helps the agent anticipate output shape and entitlement constraints.

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?

Three tightly written sentences with no filler. The batch action is front-loaded, followed by the crucial per-row download-link behavior and the Pro/free-tier limitation. Every sentence earns its place.

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 schema documents all ten parameters, defaults, and enums, while the description covers the two non-obvious facts an agent needs: per-row download links with one-hour validity and the Pro/free-tier limit. It does not explicitly route single-code requests to sibling tools, but the definition is sufficient for correct invocation.

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 100%, so the schema carries most parameter meaning. The description reinforces the items shape by mentioning rows with their own value and file name, but it does not add parameter-level detail beyond what the schema already provides.

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 opens with a specific verb and resource: 'draw many barcodes or QR codes at once from a list of rows, each with its own value and file name.' This clearly distinguishes the batch tool from the single-code siblings like barcode_create and qr_create.

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 gives a clear invocation context: use this when you need many codes at once from a list of rows. It does not explicitly name the single-code siblings as alternatives for when-not to use it, so the exclusion guidance is implicit rather than explicit.

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