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

With no annotations supplied, the description carries the full behavioral burden. It does useful work by disclosing the response shape (status, lines, totals, validity, order id) and signaling that order id is populated only after ordering, which is real lifecycle context. It stops short of stating that this is a non-mutating read, whether it requires ownership/authentication, or what happens for an invalid or expired quote.

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 front-loaded sentence with the action first and the returned fields as a compact list. Nothing is redundant and nothing needs to be moved forward.

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 one-parameter getter with no output schema, the description usefully compensates by enumerating the fields returned. It is nearly complete; the remaining gaps are error and permission behavior, which matter less for a read-only lookup.

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?

There is one parameter, quote_id, with 0% schema description coverage, so the schema gives only type and uuid format. The description's "one of your quotes" adds a meaningful constraint that the id must reference a quote owned by the caller, but it does not say where the id comes from or how it behaves if it names someone else's quote.

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 and resource ("Get one of your quotes") and enumerates exactly what comes back: status, lines, totals, validity, and order id. This distinguishes it implicitly from quote.request and quote.cancel, though it never names those siblings to make the contrast explicit.

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?

Usage is only implied: you fetch a quote you already have an id for. There is no statement of when to prefer this over quote.request or order.get, no prerequisite about obtaining a quote_id, and no guidance for the not-found or expired cases. The phrase "once ordered" hints at lifecycle positioning but doesn't spell it out.

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