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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by clarifying that it "opens nothing by itself" (no UI or browser side effects despite being a browser-based workflow), that the output is a step-by-step guide naming screens, buttons and fields, and that no public EZ Lawn Biller API exists, which explains why browser tools are 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 purpose and the no-side-effects caveat are front-loaded, and the hand-off to cotlet_browser_* tools follows logically. However, the closing sentence enumerating 404 URLs, the FAQ and QuickBooks integration is longer than needed and competes with the operational guidance.

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 tool, the description covers what it returns (ordered steps with screens, buttons, fields), what it does not do, and what to do next. The only real gap is that it never says how the agent should specify which checklist is wanted, given the sibling inventory and service checklist 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly frames the tool as taking no input and returning instructions rather than acting on an object.

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?

"Checklist ... Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)" states a specific verb (returns guidance) and resource (in-app how-to steps), and "opens nothing by itself" distinguishes it from action tools. It never names the specific checklist topic or differentiates itself from the sibling inventory_checklist and service_checklist, so the agent must infer scope from the user's request.

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 two-step workflow: call this first to get the steps, then execute them with the cotlet_browser_* tools in the user's Cloud Browser. That is genuine when-to-use guidance with a named alternative toolset. It stops short of stating when not to use it, e.g. for direct data reads that other ez_lawn_biller_* tools already cover.

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