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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds genuinely non-redundant behavior: the tool returns instructional text (screens, buttons, fields) rather than mutating anything, and it explicitly states it 'opens nothing by itself', which prevents an agent from assuming a side effect. It also documents the absence of a public API, explaining why browser automation is the required execution channel.

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 value proposition is front-loaded in the first sentence, which is good. But the trailing API-research footnote (404 on ezlawnbiller.com/api, /developers, /docs, dated 11 Nov 2026, plus QuickBooks being the only named integration) is bulky evidentiary detail that mostly justifies the routing decision rather than helping the agent invoke the tool, so not every sentence 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?

There is no output schema, and the description compensates by saying the return is step-by-step instructions with screens, buttons and fields. It also names the downstream execution tools, so an agent knows what to do after reading the result. For a zero-parameter, read-only guidance tool this is close to complete, with only sibling-level routing left unspecified.

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 coverage is 100%, so there is nothing for the description to disambiguate. Baseline for a 0-param tool is 4, and the description correctly communicates that the call needs no arguments beyond the account 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 uses a specific verb and resource: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)'. Crucially it distinguishes itself from an action tool by stating it 'opens nothing by itself', which is the key disambiguation for a name that reads like a mutation. It does not contrast itself with near siblings such as ez_lawn_biller_automatic_payments or ez_lawn_biller_cancel_automatic_payments, so it falls short of 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?

The description prescribes the follow-up path clearly: retrieve the steps, then perform them with the cotlet_browser_* tools in the user's Cloud Browser. That is useful sequencing guidance. However, it never states when to pick this tool over the many related autopay/billing siblings, nor any exclusion condition; the when-to-use is only implied by the tool name.

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