qr-maker

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

With no annotations provided, the description carries the full burden and discloses key behavioral traits: it requires Pro tier access, returns a batch ID for polling, supports up to 100 items, allows different content and style per item, and mentions an optional webhook for notifications. However, it lacks details on rate limits, error handling, or exact response format.

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 front-loaded with the core purpose, followed by essential details in three concise sentences with zero waste. Each sentence adds critical information: tier requirement, return mechanism, and item flexibility, making it efficiently structured.

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?

Given no annotations and no output schema, the description does well by covering purpose, prerequisites, return mechanism (batch ID for polling), scale limits, and item flexibility. However, it lacks details on the polling process (e.g., how to use 'get_batch_status'), error cases, or output format, leaving some gaps for a bulk generation tool.

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 already documents the 'items' array and 'webhook_url' parameters. The description adds marginal value by mentioning 'Each item can have different content and style' for 'items', but does not provide additional syntax or format details beyond what the schema offers, aligning with the baseline for high coverage.

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 verb ('Generate multiple QR codes in bulk') and resource ('QR codes'), specifies the scale ('up to 100'), and distinguishes from the sibling 'generate_qr' tool by emphasizing bulk operations versus single QR code generation.

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 clear context for when to use this tool ('Generate multiple QR codes in bulk') and mentions a prerequisite ('Requires Pro tier or above'), but does not explicitly state when not to use it or name alternatives like 'generate_qr' for single QR codes, though the bulk focus implies differentiation.

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