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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the bar is lower. The description still adds value by disclosing the returned composition (per-piece by size, pieces, volume discount, shipping, total before tax) and the important tax exclusion at checkout. It does not cover rounding, currency, or handling of unknown items, but the key behavioral facts are present.

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 with no filler: the first front-loads what the tool returns, the second front-loads how to shape input. Every clause earns its place, including the tax and no-charge caveats.

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 correctly compensates by describing the pricing breakdown and the tax treatment, and annotations already cover the safety profile. Gaps remain on currency, rounding, quantity minimums, and behavior for unrecognized items, but nothing an agent needs to invoke the tool correctly is missing.

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 single top-level 'lines' parameter carries no schema description, but its nested properties do describe item, color, sizes, and surfaces in detail. The description's 'a line is one item in one color with a count per size' largely restates that structure and never mentions the surfaces parameter or its default. Useful clarification, but not enough to fully compensate for the low top-level coverage.

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 names a specific verb (quote/what it would cost) and resource (an order) and enumerates the pricing breakdown it produces. It is unambiguous against siblings like list_items and design_item, none of which price anything. The added 'Nothing is charged' line sharpens the intent further.

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?

It gives real input-shaping guidance ('use the sizes the customer named', 'a line is one item in one color with a count per size'), which tells the agent how to construct lines. However it names no alternative tool and gives no when-to-use or when-not-to-use conditions relative to siblings such as list_items or design_item. Routing is implied rather than stated.

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