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

Goes beyond readOnlyHint/openWorldHint by disclosing the pricing model ($0.003 USDC per call, x402), which is operationally critical context absent from annotations. It also states the return shape (symbology + decoded text). It omits limits like per-image barcode count or the 20 MB cap (that is in the schema).

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?

Two tightly packed sentences, front-loaded with the action and scope, with no redundant or filler text. Every clause (symbology list, output fields, cost) carries information.

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 read-only 3-param tool with full schema coverage and no output schema, the description covers action, scope, return contents, and cost. It only lacks guidance on multiple barcodes per image and on choosing an input parameter.

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 url/filename/file_base64 and the 20 MB limit. The description adds no parameter-level detail or guidance on choosing among the three input modes, so baseline 3 applies.

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?

States a specific verb+resource ('Read every barcode and QR code in an image') and enumerates the symbologies covered, which sharply distinguishes it from the sibling 'barcode' and from 'qr' (QR-only) and 'ocr' (general text). An agent can select it without opening the schema.

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?

No explicit when-to-use/when-not-to-use or alternative routing (e.g. 'use qr for QR-code-only output'), leaving the agent to infer from the sibling list. The enumerated symbology coverage implies scope, but no exclusion or prerequisite is stated.

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