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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description stays consistent with them while adding real context: the return content is procedural guidance, no side effects occur, and browser automation is the required execution path. The API research note (404s on /api, /developers, /docs; QuickBooks as the only integration) explains why the browser route is necessary. It does not describe output length or formatting limits, so it is not 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 core behavior and the handoff to cotlet_browser_* tools are front-loaded in the first two sentences, with zero wasted clauses. The trailing API-investigation sentence is longer than strictly necessary but does justify the browser-based approach, so it largely earns its place.

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 input parameters and no output schema, the description carries the burden of explaining returns, and it does so qualitatively (step-by-step screens, buttons, fields) plus the no-side-effect guarantee and the follow-up execution path. For a guidance-only tool this is close to complete, though it could note what to do if the guidance does not match the user's 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, so there is no parameter meaning to add and the baseline of 4 applies. Nothing in the description misrepresents the (empty) input contract.

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 concrete behavior: it returns step-by-step instructions (screens, buttons, fields) for handling technician pay in EZ Lawn Biller, and explicitly says it 'opens nothing by itself'. This resolves the ambiguity in the noun-phrase name 'technician_pay', which alone could suggest a data-retrieval tool. It does not explicitly contrast itself with nearby siblings such as ez_lawn_biller_pay_profile or ez_lawn_biller_pay_statements, keeping it below 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?

Usage is clearly routed: call this to learn the procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. The 'opens nothing by itself' clause sets a clear exclusion against expecting action from this call. It stops short of naming which sibling to use when the agent actually wants pay data rather than a procedure.

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