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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with the concrete guarantee that the tool 'opens nothing by itself'. It also adds genuinely extra context beyond annotations: the integration note that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks named as the only integration), which explains why browser automation is 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?

The operative behavior is front-loaded in the first two sentences and every clause carries information. The trailing API-availability sentence is long and enumerates dated findings, but it does justify the browser-tool handoff, so it earns most of its space.

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 output schema, the description carries the burden of explaining return values, and it does so ('returns how to do it step by step (screens, buttons, fields)'). The one gap is scope: without saying which reactivation scenario the guide covers, an agent cannot be fully confident it is the right guide for the user's request.

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 has zero parameters and is fully described, so there is nothing for the description to disambiguate. Baseline 4 applies; the description is consistent with a no-argument tool.

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 outcome: it returns step-by-step reactivation instructions (screens, buttons, fields) and 'opens nothing by itself', which clearly frames this as a guidance tool rather than an action tool. It does not, however, say what is being reactivated (customer? stopped line?) nor distinguish itself from ez_lawn_biller_reactivate_customer or ez_lawn_biller_reactivate_stopped_line, which matters for a zero-parameter tool.

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 follow-up sequencing — get the steps here, then execute them with the cotlet_browser_* tools in the user's Cloud Browser — which is useful routing. It offers no when-not guidance and no criteria for choosing this generic reactivate tool over the two more specific reactivate siblings, so selection among them is left to inference.

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