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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower, and the description still adds the decisive trait: it opens nothing by itself and only returns procedural guidance, with a separate browser tool required to act. The API-availability note explains why browser automation is the path, which is useful context an agent would otherwise lack.

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 critical 'returns instructions, opens nothing' caveat are front-loaded, which is the right order. The 'from ChatGPT, Claude or any AI agent' clause and the parenthetical API investigation detail add length without changing how an agent should call the tool.

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 guidance tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields) and what to do next (cotlet_browser_* tools). The only gap is finer scoping against sibling report tools.

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?

Zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies no input is needed, consistent with the empty schema.

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 the resource (service visit reports) and, crucially, clarifies the modality: it returns step-by-step instructions for performing the task in EZ Lawn Biller rather than fetching data. That distinguishes it from data-returning siblings at a behavioral level, though it never explicitly contrasts with close relatives such as ez_lawn_biller_visit_report_settings or ez_lawn_biller_send_visit_report.

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 prescribes a workflow: use this tool to get instructions, then execute them with the cotlet_browser_* tools. That is genuine when-to-use guidance, but there is no statement about when NOT to use it or how it differs from the adjacent visit-report tools, so the agent must infer its niche.

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