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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself', so there is no contradiction. It adds genuine beyond-annotation context: there is no public EZ Lawn Biller API (endpoints returned 404, only QuickBooks integration), which explains why browser automation is required and sets expectations that no state changes occur here.

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 claim — returns a step-by-step how-to and performs nothing — is front-loaded and clear. The API research detail (404s on /api, /developers, /docs; FAQ naming QuickBooks) is somewhat verbose but earns its place by justifying the browser-tool follow-up rather than merely asserting it.

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, read-only guidance tool with no output schema, the definition covers what it returns (step-by-step screens/buttons/fields) and what to do next. Minor gap: it does not specify how to locate or invoke the relevant cotlet_browser_* tool in the user's cloud browser session, though that is arguably the sibling toolset's responsibility.

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 schema to document and no compensation needed; the baseline of 4 applies. The description correctly implies no inputs are needed beyond the implicit user 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?

States a specific resource (automatic payments in the user's own EZ Lawn Biller account) and, crucially, clarifies the verb: the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the action. This distinguishes it cleanly from siblings like ez_lawn_biller_cancel_automatic_payments or ez_lawn_biller_offer_paypal_automatic_payments_again without needing their schemas.

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?

Gives a clear workflow: call this to get the procedure, then execute it with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. It does not explicitly state when to prefer a sibling (e.g., cancel vs. set up), but the scope is narrow and unambiguous enough that an agent can route correctly.

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