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, so the safety profile is known. The description adds genuinely new behavioral context — 'opens nothing by itself' and that the return value is step-by-step instructions (screens, buttons, fields) rather than a performed action. It stops short of describing output format or length, so a 3 rather than higher.

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 operative instructions — what is returned and what to do with it — come first, which is the right ordering. The closing sentence about the missing public API is longer than it needs to be for the caller's decision, but it justifies the browser-automation path and is not padding.

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, no-output-schema tool, the description covers what it returns (step-by-step UI instructions), what it does not do (no side effects), and how to act on it (cotlet_browser_* tools). The rationale for the browser path is supplied via the API-availability note. Only sibling disambiguation is missing.

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 the baseline is 4. Nothing in the description misrepresents the parameter surface, and it correctly frames the tool as taking no user input beyond the implicit task context.

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 the resource (text in EZ Lawn Biller) and, importantly, corrects the misleading verb by stating the tool 'Returns how to do it in EZ Lawn Biller step by step' and 'opens nothing by itself.' That reframes it from an action tool to a procedural-guidance tool, which an agent needs. It does not explicitly contrast with ez_lawn_biller_compose_email or ez_lawn_biller_send_text, leaving the 'text vs email vs send' distinction to inference.

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 workflow guidance is useful: get steps here, then execute with the cotlet_browser_* tools in the user's Cloud Browser. However, there is no explicit when-to-use/when-not-to-use or routing advice against the closely named siblings (compose_email, send_text, text_all), so the agent must guess which of these to call first.

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