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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral detail: it cross-checks against the catalog, returns per-line matches, provides variant_id and price, and signals items that still require an execution/option to be chosen. No contradiction with annotations was found.

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?

A single dense sentence conveys the input format, the catalog-matching behavior, and the output semantics without wasted words. The purpose is front-loaded, and every clause adds necessary 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?

There is no output schema, so the description reasonably carries the burden of explaining results: per-line found items, variant_id for cart, price, or the 'need to choose execution' marker. It is complete enough for an agent to call the tool and understand the response, though exact JSON shape and not-found behavior are not spelled out.

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 input schema has no description for the required 'text' parameter, and schema coverage is 0%. The description compensates by explaining the expected text structure: one line per position with article or name and quantity. While it doesn't give separator or formatting examples, it provides the essential meaning that the schema itself lacks.

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 uses a specific verb ('parse') and clear resource ('specification or estimate'), and explains exactly what happens: each line is matched against the catalog and returns per-line findings. This distinguishes it from related tools like find_by_sku and search_products, which operate on single items rather than full spec text.

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 gives clear context for when to use this tool: when the user provides a specification or estimate as multi-line text with article/name and quantity per line. It also implies the result feeds cart selection via variant_id. However, it does not explicitly mention when not to use it or name alternative tools for single-item lookup.

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