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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that by saying it 'opens nothing by itself.' Beyond the annotations it adds genuinely useful behavior: the return is an instructional walkthrough rather than data, and the absence of a documented API (with dated evidence and the QuickBooks-only integration note) explains why UI guidance is the mechanism.

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 core guidance is stated up front, but the opening clause ('from ChatGPT, Claude or any AI agent') is filler and the API-availability evidence is dense boilerplate appended to every such tool. The middle semicolon splice joining the instruction-return and the browser handoff is hard to parse.

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, read-only guidance tool with no output schema, the description covers what it returns, that it performs no action, and how to act on the result. It does not describe the shape or granularity of the returned steps, but nothing essential for correct invocation is missing.

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 no parameter semantics to explain; baseline 4 applies. The description correctly implies no inputs are needed.

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 states a specific outcome: it returns step-by-step instructions (screens, buttons, fields) for recording a lawn-treated entry in the user's EZ Lawn Biller account, and explicitly says it opens nothing itself. That separates it from action-performing siblings, though the leading phrase 'Lawn Treated in the user's own EZ Lawn Biller account' is a noun fragment rather than a clean verb+resource statement.

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 use context and an explicit follow-on path: get the steps here, then execute them with the cotlet_browser_* tools in the Cloud Browser. It also signals why this route is needed (no public API), but it does not name a specific sibling alternative or state when not to use it.

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