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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety and repeatability are covered. The description adds value annotations cannot: it discloses the shape and depth of the payload (customer, status, all options, each with lines and total), telling the agent this is a deep read rather than a summary. It stops short of noting behavior when an id is stale or not found.

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 sentence with zero waste, front-loading the returned object before its nested contents. It is telegraphic to the point of reading like a field list rather than a sentence, but nothing is redundant or padded.

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 read with full annotation coverage, the description supplies the return shape that the absent output schema would otherwise carry. However, it leaves the agent without workflow context — how the id is obtained, what happens with an invalid or option id, or how the result differs from get_invoice/get_job — which matters given a crowded sibling set.

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 100% and the single parameter is fully documented in-schema, including the notable fact that an est_… option_id also works. The description adds no parameter meaning of its own; 'every option' is the closest hint at the estimate/option duality, which the schema already handles explicitly. Baseline 3 applies.

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?

Names a specific resource (one estimate) and enumerates what is attached to it — customer, status, options, lines, total. An agent can tell this is a single-record read rather than a list or a mutation, distinguishing it from siblings like list_estimates or create_estimate. It falls short of 5 only because the verb is elided ('One estimate with…') rather than stated.

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?

There is no explicit when-to-use statement and no comparison to any alternative — not even to get_invoice/get_job for adjacent lookups, nor to add_estimate_option which operates on the options mentioned here. The only implicit cue is that it takes an id, which implies retrieval after a listing call. An agent must infer the retrieval-after-list workflow entirely.

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