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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: 'partial means some prices need the business' explains a response status, and 'each product and option once' states a uniqueness constraint. It still omits limits such as the 30-line cap, quantity bounds, and whether estimation triggers any side effects.

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?

Only two sentences and no padding, which is good, but they are front-loaded with fragmented parameter prose ('Use product_id and variant_id from products; each product and option once, with a quantity') instead of the tool's purpose. The clipped grammar makes the constraint rules harder to parse than necessary.

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 no output schema, the description does at least hint at return content (items, total, and a 'partial' price status) and gives the key calling convention of sourcing IDs from products. For a three-parameter, read-only estimation tool that is reasonably complete, though fulfillment and line metadata remain unexplained.

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 0%, so the description must carry parameter meaning, and it does partially: it names product_id and variant_id and points to the products tool as their source, and ties quantity to each line. It says nothing about the required 'business' parameter, the fulfillment enum (pickup/delivery), or the item_id and fields properties, leaving a meaningful gap.

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 title 'Estimate an order' and the phrase 'Review the items and total with the customer' imply it prices a basket of products, but the description never states plainly what the tool computes or returns. It opens with parameter instructions rather than a verb+resource statement, so the agent must infer the purpose from the title. Sibling tools like request_order and checkout_order are only weakly distinguished.

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 closing clause 'Review the items and total with the customer before request_order' gives a concrete sequencing rule and names a sibling, which is useful routing. However, it does not say when NOT to use the tool or how it differs from checkout_order or product lookup. Usage is implied through workflow position rather than stated as explicit conditions.

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