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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false; the description adds genuinely new context by asserting it "opens nothing by itself" (no side effects despite the browser-oriented naming) and that no public API exists, so browser automation is the only path. It stops short of describing the shape or length of the returned steps beyond "screens, buttons, fields."

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 behavior and the handoff to cotlet_browser_* tools are front-loaded in the first two sentences. The trailing API-research sentence is longer than needed (listing 404 URLs, dated research, and the QuickBooks FAQ detail) but does justify why the tool is browser-based, so it largely earns its place.

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, no-output-schema instruction tool, the description covers what is returned (step-by-step screens, buttons, fields), that it performs no action, and what to use next. What is missing is any characterization of what a "held billing reminder" is or what the user's account state looks like, which would help an agent frame the steps.

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 empty, so there is no parameter meaning for the description to add. Baseline 4 applies; the description correctly implies nothing about inputs.

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?

"Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself" states a specific verb (returns instructions) and resource (held billing reminders), and makes the unusual nature of the tool explicit. It falls short of 5 because it never distinguishes itself from the very similarly named sibling ez_lawn_biller_review_held_billing, so an agent cannot tell from the text which one to pick for a review task.

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?

The description gives a clear follow-on path: "then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser," which tells the agent this tool is a read-the-guide step, not the action itself. However, it offers no when-to-use vs. when-not guidance against the near-identical siblings (ez_lawn_biller_review_held_billing, ez_lawn_biller_bill_held_periods, ez_lawn_biller_skip_held_periods), leaving selection to inference.

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