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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself' and 'opens nothing' behavior, which is consistent. It adds genuine context beyond the annotations by stating what the caller receives (screens, buttons, fields) and by documenting the API-discovery finding that constrains the workflow.

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?

Core behavior is front-loaded and clear, but the second sentence is a long run-on that mixes the return value, the no-side-effects guarantee, and the follow-on browser tools. The trailing API-research sentence is defensible context but is dense and reads more like a research note than tool documentation.

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 guidance tool with no output schema, the description covers what is returned and what to do next, which is the essential information. Minor gaps remain, such as whether any account/login state is assumed before the returned steps are usable, but nothing an agent needs to select or invoke it correctly 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 and the schema is a closed empty object, so there is no parameter meaning left to convey. Baseline for a 0-param tool is 4, and nothing in the description adds confusing or contradictory parameter guidance.

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 resource (a refund in the user's EZ Lawn Biller account) and makes the crucial clarification that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the refund. That distinction separates it from any execution sibling, though the task-style opening sentence ('Refund in the user's own ... account') could momentarily read as an action before the second sentence corrects it.

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 an explicit workflow: call this to get steps, then perform them with the cotlet_browser_* tools in the user's Cloud Browser, and it explains why (no documented EZ Lawn Biller API, so the browser path is the only route). It does not explicitly name sibling alternatives or exclusions, but the follow-on path is unambiguous.

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