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

Beyond the readOnly/destructive/openWorld annotations, the description adds real operational context: accepted input forms (file or public URL), the exact return fields (decoded value, symbology), tier-gated extras (GTIN, orientation, corners, all barcodes in image), and a concrete cost of 10 credits. That cost and plan-gating disclosure is genuinely useful and not present in structured fields. It stops short of stating behavior on undecodable images or multiple-barcode defaults.

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?

Front-loaded with purpose, followed by the symbology list, then output/tier details and cost. Single tight paragraph with no filler, though the long comma-separated code list is slightly heavy relative to the rest.

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?

With an output schema present, the description needn't document returns in depth, yet it still summarizes them and adds pricing and plan-gating that schemas cannot express. Remaining gaps are small: whether multiple-barcode results are only available on paid tiers, and what happens on an image with no readable barcode.

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 'image' parameter, so the schema already documents file-vs-URL input. The description restates 'uploaded image or an image URL' and adds the accepted formats (also in the schema), contributing little new meaning. Baseline 3 for a fully documented schema.

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+resource ('decodes 1D barcodes') and enumerates the supported symbologies, so an agent knows exactly what it does. It implicitly separates itself from siblings QRCodeReader and BarcodeGenerator by scoping to 1D decoding, but it never names those alternatives explicitly.

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?

Usage is only implied: the enumeration of 1D symbologies suggests when this tool applies and the scoping away from QR codes is inferable from siblings, but there is no explicit 'use this when / use X instead' routing. No prerequisites or failure conditions are stated.

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