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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description usefully reinforces that profile by stating it 'opens nothing by itself' and is a guidance-only call, which directly explains the readOnly annotation. It also discloses an integration limit: no public API exists (404s on /api, /developers, /docs, with QuickBooks the only named integration).

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 core instruction comes first: what the tool returns and the follow-up flow with cotlet_browser_*. The audience enumeration ('ChatGPT, Claude or any AI agent') is mild filler, and the API-research paragraph is long for a closing note, though it does carry real information.

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 and no parameters, the description must carry the return-value burden, and it does: it says the result is step-by-step screens, buttons and fields. The next-step handoff to cotlet_browser_* covers the execution gap that a guidance-only tool creates. The only missing piece is sibling routing among the pause variants.

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 there is nothing for the description to disambiguate at the argument level. The baseline of 4 applies; the description correctly avoids inventing parameter details and instead frames what the call will return.

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, the user's EZ Lawn Biller account, and a specific outcome: it returns step-by-step instructions (screens, buttons, fields) for pausing. It also clarifies that the tool produces guidance rather than performing the pause, which resolves the tension between the name 'pause' and readOnlyHint=true. It does not, however, distinguish this tool from the sibling auto_pause or scheduled_pause variants.

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?

The description gives a clear workflow: use this tool to get the steps, then execute them with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. That is useful when-to-use context. But it never says when to choose this tool instead of ez_lawn_biller_auto_pause or ez_lawn_biller_scheduled_pause, and it gives no exclusions.

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