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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context beyond this: it explicitly warns that 'read' doesn't guarantee external scanner compatibility and 'not read' doesn't condemn the label due to photo issues. This honest disclaimer goes beyond the annotations and is the kind of context that helps agents manage expectations.

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 concise and well-structured. It front-loads the core purpose, specifies formats, and then adds the behavioral disclaimer in a compact, context-rich clause. Every sentence earns its place, and there's no filler 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?

For a tool with one parameter, full schema coverage, and a clear output (readback results), the description covers the essential context. It explains the input type, the purpose, and provides behavioral caveats. It doesn't detail the response structure, but since there's no output schema, it could benefit from a note on what the response includes (e.g., barcode values), but this is a minor gap.

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 100% for the single parameter, so the schema already documents what image_base64 is. The description mentions that the image should be of a printed label, which aligns with the parameter, but adds little additional semantic detail beyond emphasizing that it's a photo/scan of a printed label. Given high coverage, baseline 3 is appropriate.

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 identifies the tool's purpose: decoding barcodes from printed label images. It specifies supported image formats and emphasizes the 'read back' aspect, which distinguishes it from other tools in the sibling list (e.g., barcode_png, image_to_zpl). The verb 'decode' and resource 'printed label' are specific and unambiguous.

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 when to use this tool (when you have a printed label image and need to know what a decoder reads), but it doesn't explicitly mention alternatives or when NOT to use it. It could be clearer about when to use barcode_png (which might be for generating barcodes) or image_to_zpl (converting images to ZPL), but the user can infer this from the description.

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