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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: required access level (owner or team admin; PRO plan and above) and a preview of what the read returns (prices, open assumption, on/off flags). It does not mention rate limits or pagination, but for a single-object read that is minor.

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?

Four short sentences, with the action front-loaded and the constraint/permission notes trailing. Efficient, though 'in plain words' and the double 'Essays/Estimates' phrasing are read twice before parsing cleanly.

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?

No output schema exists, and the description compensates by enumerating the three things returned plus the access requirement and ordering hint. A single-optional-param read tool needs little more; only the return shape (structured object vs. text) remains unspecified.

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?

Only one parameter with 100% schema description coverage, so the schema already explains that businessProfileId should be omitted for the default business. The description adds nothing about the parameter; 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?

States a specific verb (read) and concrete resources: Estimates prices, any open assumption, and whether Estimates and quoting-on-calls are enabled. That distinguishes it from the write-side siblings (estimates_update_prices, estimates_set_enabled), though it never names them explicitly and the phrase 'prices in plain words' is slightly awkward.

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?

'Call first' is an explicit sequencing instruction that tells the agent to hit this before the other estimates_* tools — genuinely actionable ordering guidance. It lacks an explicit 'use X instead when...' exclusion, so it stops short of a 5.

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