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

Annotations already establish readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false. The description adds genuinely non-redundant behavior: the result is textual step-by-step navigation content rather than an executed action, and taking action requires a separate Cloud Browser toolset. It does not describe output shape or length, which limits it slightly.

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 opening clause about ChatGPT, Claude or any AI agent is filler that does not help selection, and the trailing paragraph about 404s on ezlawnbiller.com/api and QuickBooks being the sole integration is background rationale rather than decision-relevant guidance. The core instruction is front-loaded, but roughly a third of the text could be cut without loss.

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 says what comes back (screens, buttons, fields) and how to proceed afterward, which is the information an agent needs to act. Only the return format and any preconditions on the Cloud Browser session are left implicit.

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 no parameter meaning to convey. Baseline for a parameterless tool applies, and the description correctly avoids 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?

The description states a specific effect: it "Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)." The clarifying clause "opens nothing by itself" resolves the ambiguity created by the title, which could otherwise imply an action. It never names a sibling tool from the EZ Lawn Biller family, so differentiation relies on the reader already knowing the catalog.

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 use condition: call this to learn the procedure, then "do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." The two-step relationship between the guidance tool and the execution tools is explicit. It stops short of naming when this is the wrong choice versus a sibling like ez_lawn_biller_technician_pay.

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