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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating the tool 'opens nothing by itself', which prevents an agent from assuming a real deletion occurs. It also adds context the annotations cannot carry: the absence of a public API (404s on /api, /developers, /docs) and the resulting need for browser automation.

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 behavior and the browser handoff are front-loaded in the first two sentences, but the closing API-availability sentence is long and tangential to invocation. The opening phrase ('...from ChatGPT, Claude or any AI agent') adds words without adding decision-relevant information.

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?

With no parameters and no output schema, the description supplies exactly what is missing: what is returned (screens, buttons, fields), what the tool does not do (opens nothing), and which tool family performs the actual action. An agent has enough to call it correctly and follow up.

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 schema baseline is 4 and there is no parameter meaning for the description to compensate for. The description does implicitly raise the question of how the target customer is identified when no argument exists, but that is a design issue rather than a documentation gap in scope 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?

The description names a specific verb and resource ('Remove customer') and scopes it to 'the user's own EZ Lawn Biller account', then clarifies the deliverable is step-by-step instructions rather than the deletion itself. It does not distinguish this from close siblings like ez_lawn_biller_cancel_customer or ez_lawn_biller_edit_customer, so an agent must infer the boundary.

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 clearly explains the execution model: the tool returns a walkthrough and 'opens nothing by itself', after which the agent should use the cotlet_browser_* tools in the Cloud Browser. That is useful workflow guidance, but there is no explicit when-to-use versus cancel_customer or reactivate_customer, and no stated preconditions or exclusions.

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