Add barcode / QR code

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

Annotations already indicate idempotency and non-destructiveness. The description adds important behavioral details: no URL-encoding of data, auto-computation of EAN-13 check digit, and error correction level recommendations for printed media. It does not describe output format or error 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 well-structured with a clear opening sentence, a bullet list of formats with use cases, and a concrete recipe example. It is not overly verbose, though slightly more conciseness could be achieved.

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 the complexity (10 parameters, 4 enums, output schema exists), the description covers key aspects: formats, data constraints, error correction, and an example. It does not explain outputMode/outputPath, but the output schema likely covers return values.

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 description adds significant meaning beyond the input schema by providing usage context for each format, concrete data format examples, and guidance on error correction levels. For instance, it clarifies that data should be raw payload and not URL-encoded.

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 that the tool generates a single-page PDF embedding a barcode or QR code. It lists specific barcode formats with examples, distinguishing it from sibling PDF tools like add_attachment or add_form.

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 guidance on when to use each barcode format (e.g., QR for URLs, code128 for SKUs, ean13 for retail) and includes a recipe for a common use case. However, it does not explicitly mention when to avoid this tool in favor of alternatives.

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