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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds the genuinely useful clarification that despite being a POST, nothing is ordered or billed, which prevents an agent from misreading the verb as a write. It does not cover rate limits or whether prices can be stale, so it falls short of full disclosure.

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?

Three short sentences: what it returns first, the safety clarification second, the endpoint last. Every sentence carries information and nothing is repeated unnecessarily.

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 single-parameter, read-only lookup with annotations covering the safety profile and no output schema, the description says enough to call it correctly. A hint about what the 'breakdown' contains would close the remaining 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%, including nested sku/quantity descriptions and the 50-item cap, so the baseline is 3. The description restates the batch limit and 'at given quantities' but adds no format guidance (e.g. SKU vs product code selection criteria) beyond what the schema already documents.

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 pair ('price and price breakdown') plus the concrete scope: up to 50 product codes or virtual inventory SKUs at given quantities. It is clearly a pricing lookup rather than an order/product-detail call, though it does not name a sibling to contrast against.

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?

'Nothing is ordered or billed' implies the intended use case of quoting/estimating prices before committing to an order, but the description never states when to prefer this over finerworks_get_product_details or finerworks_get_order, nor any exclusion.

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