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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description nonetheless adds the important operational fact that it "opens nothing by itself" and only returns instructions, which prevents the agent from assuming a side effect occurred. It also discloses why browser automation is required (no public API, with the 404 evidence), which is genuinely useful context beyond the annotations.

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 two core sentences are front-loaded and do the real work: what it returns, that it has no side effects, and which tools to follow up with. The closing note on the missing public API is longer than strictly necessary (specific URL paths and a date), but it justifies the browser-based workflow rather than padding for its own sake.

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, output-schema-less guide tool, the description covers the essentials an agent needs: what it returns (ordered screens/buttons/fields), that nothing is opened, and the handoff to cotlet_browser_* tools. It stops short of describing how the instructions are formatted or how long/detailed the output will be, which is a minor gap given no output schema exists.

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 implies a context-free, argument-free invocation by stating the tool simply returns instructions.

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 clearly states this is a step-by-step knowledge tool ("Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)") for recurring service setup, which is a distinct verb+resource from the actual mutation siblings. It is slightly weakened by the opening fragment "Recurring service in the user's own EZ Lawn Biller account," which is a noun phrase rather than a statement of what the tool does, so the agent must read to the second sentence to learn the behavior.

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 explicit sequencing guidance: call this first for instructions, then "do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That is a clear when-to-use and what-to-do-next contract. It does not, however, distinguish this from closely named siblings such as ez_lawn_biller_recurring or ez_lawn_biller_recurring_billing, leaving the agent to guess which recurring-related entry point to pick.

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