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 is consistent with that and reinforces it by saying it 'opens nothing by itself'. It adds useful context beyond the annotations: what the response contains (step-by-step screens/buttons/fields) and the follow-up execution path via browser tools.

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 purpose and the 'returns guidance, does not act' constraint are front-loaded in the first two clauses, which is good structure. The trailing API-investigation note (404s on /api, /developers, /docs, QuickBooks as the only integration) is somewhat verbose but does justify why the UI-instruction approach is used.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description covers what it returns, that it performs no actions, and which tool family to use next. The only modest gap is that it does not sketch the shape or granularity of the returned steps, but that is acceptable given there is no output schema.

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 beyond what the empty schema already conveys. Baseline for a parameterless tool is 4, and nothing in the description misleads about 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?

The description names a concrete resource and outcome: it returns step-by-step instructions (screens, buttons, fields) for performing payment retries in the user's own EZ Lawn Biller account. It implicitly distinguishes itself from action-performing siblings by stating it 'opens nothing by itself', though it never names a specific sibling tool such as ez_lawn_biller_record_payment.

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 context: this is the tool to call when the user wants to know how to do payment retries, and it explicitly says the actual execution should be done with the cotlet_browser_* tools in the user's Cloud Browser. There is no explicit exclusion list against the many sibling tools, but the when-to-use and the hand-off alternative are both stated.

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