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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the estimate carries up to five options, each with a name and total, and a 'Converted' state appears once it becomes a job. The Cotlet API key requirement is also disclosed.

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 description is under-structured and repeats itself: 'each option, its line items and total' and 'Each option has a name, line items and a total' convey the same information twice. The auth note trails at the end rather than being grouped logically, so a sentence could be trimmed.

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 carries the return-value burden and does so reasonably well, describing the estimate, its options, line items, totals, and Converted status. The main remaining gap is pagination- or limit-related behavior, but for a single-record fetch with one required param it is largely complete.

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 a single parameter with 100% schema coverage, and the schema already says 'Estimate ID from list_estimates.' The description adds no syntax or format detail beyond that, so the baseline 3 for high coverage 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?

The description states a specific resource and scope: it returns one estimate with its options, line items, and total. The singular 'Returns one estimate' implicitly distinguishes it from list_estimates. It is clear but the opening sentence is slightly garbled ('Estimate with each option, its line items and total'), reading more as an output summary than a crisp action statement.

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 offers one workflow hint ('Use the option name in convert_estimate_to_job') and an auth prerequisite, which implies you use this to fetch a single estimate before converting. However it never says when to use this versus list_estimates or get_job, and gives no explicit exclusions.

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