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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false; the description adds the meaningful extra that it "opens nothing by itself," so the agent knows this call has no side effects and must be followed by browser tooling. The API-availability note (404s on /api, /developers, /docs; QuickBooks named as the only integration) further explains why a browser path is required, which is context annotations cannot supply.

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 largely restates the tool name and title ("Customer late fees in the user's own EZ Lawn Biller account"), spending space without adding information. The remaining content — guidance-only behavior, the browser hand-off, and the API-absence rationale — is well ordered and earns its place, but the long API sentence could be trimmed.

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?

With no parameters and no output schema, the description carries the burden of saying what comes back, and it does: step-by-step screens, buttons, and fields. It also names the follow-on tools needed to actually perform the task, leaving little an agent needs to infer; only the distinction from the similar late-fee sibling 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 per the baseline this is a 4. The description correctly implies no input is needed, and there are no parameters for it to leave ambiguous.

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 concrete behavior: it "Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself" — an instruction-lookup tool rather than an action. That is a real, specific purpose an agent can act on, though the opening clause mostly restates the tool name and there is no explicit differentiation from the near-identically named sibling ez_lawn_biller_late_fees.

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 does route the agent forward: call this to get the steps, "then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That is useful implied workflow, but there is no when-not-to-use guidance and no statement of how this differs from ez_lawn_biller_late_fees or ez_lawn_biller_waive_this_late_fee, so the agent must guess between overlapping late-fee tools.

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