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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the valuable behavioral fact that this is an advisory/guidance tool that performs no action itself and hands off to browser tools. The note that EstimateOne's External API is not self-service and is read-only explains why the browser route exists, a useful constraint. It does not describe the shape/detail of the returned steps beyond 'screens, buttons, fields'.

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?

Front-loaded and short: what it returns, that it does nothing by itself, and what to do next, in that order. The closing API note is tangential trivia that a strict reader could cut, but it justifies the browser workflow.

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 parameters, no output schema, and full annotation coverage, the only real burden is explaining what comes back and what to do next, both of which are addressed. It stops short of detailing the format or granularity of the step-by-step guidance.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description properly refrains from inventing inputs.

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?

'Revise quote in the user's own EstimateOne account' gives a specific verb and resource, and the follow-up sentence corrects the name's implication by stating the tool returns step-by-step instructions rather than performing the revision. The distinction from action tools like estimateone_set_quote_response or estimateone_submit_quote is implied by 'opens nothing by itself' but never stated by name.

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 clearly routes the agent forward: get the steps here, then execute with the cotlet_browser_* tools in the Cloud Browser. It does not explicitly say when to prefer this over the sibling quote-mutation tools, but the 'opens nothing by itself' line effectively excludes it from being a direct action path.

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