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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description backs that up with 'opens nothing by itself' while also stating what the return payload contains (screens, buttons, fields). It additionally discloses a prerequisite the annotations cannot express: the actual work happens through cotlet_browser_* tools in the user's Cloud Browser. It does not cover rate limits or what happens if no browser session exists.

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 correction (returns instructions, opens nothing) is front-loaded, and the follow-up browser instruction comes second, which is the right order. The final API-audit sentence is long relative to its value and is anchored to a dated finding ('11 Nov 2026') that will go stale, and 'the user's own EZ Lawn Biller account' is repeated as 'the user's EZ Lawn Biller Cloud Browser'.

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 and no output schema, the description carries the burden of explaining what comes back, and it does: step-by-step screens, buttons and fields, with no side effects. It also explains why browser automation is the path by noting no public API exists. A little more detail on where the returned steps begin (which screen or menu) would close the remaining gap.

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; the baseline for a 0-param schema applies. No parameter claims are made that could mislead an agent.

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 definition names a specific resource (pay statements) and, crucially, corrects the executing verb in its own name: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That tells an agent this is a guidance tool, not a mutation. It stops short of distinguishing itself from nearby statement siblings such as ez_lawn_biller_email_all_statements or ez_lawn_biller_statements.

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 explicit sequencing: read the returned steps, then execute with the cotlet_browser_* tools inside the user's EZ Lawn Biller Cloud Browser. That is clear context for how the tool fits into a workflow. It offers no when-not-to-use guidance and does not point at or rule out any of the statement/email siblings, so selection between alternatives is left to inference.

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