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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and 'opens nothing by itself' is largely a restatement of that. It does add genuinely new behavioral context: the return shape (screens, buttons, fields) and the researched fact that no public API exists, so browser automation is the only route.

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 first sentence front-loads the core purpose well, but the closing paragraph about the official API investigation (404s on /api, /developers, /docs, QuickBooks as the only named integration) is long and only marginally relevant to invoking this tool. It reads as research notes appended to a definition.

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 help tool with no output schema, the description covers what it returns, that it has no side effects, and what to do next. Only the lack of explicit sibling differentiation keeps it from being fully complete.

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 no parameters, so there is nothing for the description to disambiguate; the schema is closed and complete. Baseline 4 applies for a zero-parameter 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 resource: returns step-by-step manual instructions (screens, buttons, fields) for EZ Lawn Biller, and explicitly notes it opens nothing by itself. It is separable from the many mutation siblings, though it does not explicitly contrast with close neighbors like ez_lawn_biller_estimate_help, leaving the agent to infer the scope difference.

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 workflow: call this to get the steps, then perform them with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. That is actionable context, but there are no explicit when-not conditions or guidance on choosing between this and the similarly named *_help / manual_adjustment siblings.

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