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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that, reinforcing that the tool performs no action. It adds genuinely useful context beyond the annotations: the return value is a screen/button/field walkthrough, and a separate browser tool set is required to actually cancel.

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?

Purpose and the 'opens nothing by itself' caveat are front-loaded, and the browser-tool handoff follows logically. The closing API archaeology (404s on /api, /developers, /docs, a date, and a QuickBooks note) is longer than needed to justify the browser-automation path and could be compressed to one clause.

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 guidance tool, the definition covers what it returns, what it deliberately does not do, and which tools complete the task. The only residual gap is sibling disambiguation, which is a routing nicety rather than a blocker to correct invocation.

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. The description adds nothing about inputs because there are none to explain, which is appropriate here.

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 verb and resource ('Cancel customer') and immediately clarifies the actual mechanic: it returns step-by-step instructions rather than performing the cancellation. That distinction is valuable, but the definition never differentiates itself from close siblings like ez_lawn_biller_cancel or ez_lawn_biller_remove_customer, so an agent cannot disambiguate the family on the description alone.

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?

It gives a clear downstream workflow: get the steps here, then execute them with the cotlet_browser_* tools in the Cloud Browser, and it notes that the tool opens nothing itself. It stops short of saying when to prefer this over the sibling cancel/remove tools, so usage is implied rather than fully routed.

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