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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds genuinely new behavioral context beyond them: it 'opens nothing by itself' and returns procedural instructions rather than data, so the agent must follow up with browser tools. It also explains why the procedural route exists — no documented API. It does not describe the shape or length of the returned steps, which keeps it from a 5.

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 key fact — that this returns instructions and opens nothing — is front-loaded and clear. However, 'from ChatGPT, Claude or any AI agent' is filler, and the four-clause API-not-found sentence (URLs returning 404, FAQ and manual referencing QuickBooks) is longer than needed to justify the procedural approach.

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 burden of describing the return value, and it does so at a useful level: step-by-step screens, buttons and fields. It also makes the tool's role in a two-step workflow explicit (guidance here, execution via cotlet_browser_*). Missing only specifics such as whether the response is scoped to a particular account or UI version.

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 and the schema is an empty closed object, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies no arguments are needed to request the estimates-list walkthrough.

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 the resource ('Estimates list in the user's own EZ Lawn Biller account') and, crucially, clarifies that the tool returns step-by-step guidance rather than performing the action: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from the sibling ez_lawn_biller_* action tools. The verb is implicit rather than explicit ('list' reads like an action until the second sentence corrects it), which keeps it just short of a 5.

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 gives a clear usage path: get the steps here, 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' That names the alternative and the follow-up. It does not state exclusions (e.g., when another estimates-related sibling would be preferred) or prerequisites such as being logged in, so it stays at 4.

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