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

Adds substantive behavior beyond the annotations: it returns procedural steps and "opens nothing by itself," so the readOnlyHint is explained in operational terms, and it names the follow-up execution path (browser tools). The note that no public EZ Lawn Biller API exists explains why the browser route is required, which prevents an agent from attempting an API call.

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 is front-loaded in the first clause, and the second sentence gives the actionable handoff. The third sentence (dated 404 research on ezlawnbiller.com/api, /developers, /docs) is provenance that is only marginally relevant to invoking the tool and could be compressed.

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 parameterless, read-only instruction tool with rich annotations and no output schema, the definition covers what it returns and what to do next. The only minor open point is which customer the returned steps apply to, but with zero input parameters the answer is necessarily generic and does not block 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; schema coverage is 100% and there is nothing further to document. The description correctly adds no param noise.

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+resource ("Reactivate customer in the user's own EZ Lawn Biller account") and immediately clarifies that what it actually produces is step-by-step guidance, not the reactivation itself. It stops short of differentiating from the close sibling ez_lawn_biller_reactivate (and reactivate_stopped_line), so an agent must infer the distinction from names.

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 usage pattern: call this to get the screens/buttons/fields, then perform the action with cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. It does not state exclusions (e.g., when to prefer ez_lawn_biller_reactivate), so the when-not side is left implicit.

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