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

With no annotations, the description carries the burden and does disclose meaningful traits: batch cap, output modes, deduplication, filtering semantics, and pricing. It omits error/rejection behavior, rate limits, or what happens on partial failures.

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 sentences front-load the core capability and fast-follow with a dense but organized feature list and pricing. It's information-dense without 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?

Given a 6-param nested tool with no output schema, the description covers the main operational surface (modes, filtering, dedup, limits). It doesn't describe the response structure, which the absence of an output schema arguably warrants noting.

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%, so baseline is 3. The description adds value beyond the schema by enumerating the supported modes (full/errors-only/summary), filtering dimensions (validity, type, error type), and the pricing model, giving context the raw enum names don't convey.

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 (validate and analyze barcodes) and scope (up to 100,000 EAN-8, UPC-A, EAN-13, GTIN-14) clearly. It doesn't contrast itself against the sibling analyze_barcode, so an agent must infer the difference (batch vs. single).

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 'in one request' and 100,000-cap framing implies this is for bulk processing versus a single-barcode tool, but it never names analyze_barcode or states when to choose one over the other. No explicit exclusions.

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