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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-obvious behavior beyond that: the tool returns procedural instructions rather than performing anything, and it documents that no public EZ Lawn Biller API exists (verified 404s on /api, /developers, /docs), which explains why browser tools are required.

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?

Front-loaded and dense: purpose, self-limitation, and next step arrive in the first two clauses. The trailing API-audit sentence with a specific dated verification note is somewhat verbose and reads like provenance metadata, costing a point, but it does explain the browser-tool dependency.

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 this covers the essentials: what it returns (step-by-step screens/buttons/fields), that it is inert, and how to act on the result. It does not state whether the returned instructions are generic or tailored to the user's account state, which is the main remaining ambiguity.

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 input schema is an empty object with zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless lookup.

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 makes clear this is a knowledge/how-to tool: it "[r]eturns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)" for the Payments workflow, and explicitly contrasts itself with the browser automation path. That is a specific verb+resource, though it never mentions the closely related siblings (e.g. ez_lawn_biller_automatic_payments, ez_lawn_biller_export_payments) that cover adjacent payment topics.

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?

Strong workflow guidance: "opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ... Cloud Browser" tells the agent exactly what this tool does and what to do next. It lacks explicit when-not guidance or differentiation from sibling payment tools, which keeps it below a 5.

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