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

Beyond the readOnlyHint/openWorldHint annotations it adds substantive context: it reads only the saved quote, contacts no shop, places nothing, charges nothing, and requires a Maglev API key. It also pre-discloses the semantic shape of the result (what the total includes and excludes, firm vs budgetary), which is exactly the kind of behavior an agent needs before promising a price to a user.

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?

The triggering condition and the safety disclaimer ('places nothing, charges nothing') are front-loaded, then the return contents are enumerated in one compact clause. There is no repetition of the title and no filler; every clause carries new 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 must describe return values, and it does: total composition, exclusions (tax, US import duty), price firmness, and terms. Combined with the auth requirement and the read-only guarantee, an agent has everything needed to call this correctly and set user expectations.

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?

With a single parameter at 100% schema coverage, the schema already documents quote_id fully. The description adds only the provenance link back to get_quotes, which the schema description also states, so the added meaning is marginal beyond the baseline.

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 opens with a specific verb and resource ('Preview an order') and immediately enumerates the returned content: quoted total, shipping, exclusions, price firmness, and ordering terms. It clearly separates itself from get_quotes (source of the quote_id) and place_order (which actually orders), so an agent can tell the three apart without opening any schema.

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 a concrete trigger ('when the user wants to order one of the offers from get_quotes') and embeds the prerequisite that quote_id must originate from get_quotes. It never explicitly names place_order as the next step or states when-not to use this tool, so the routing is strong but not fully explicit.

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