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, so the low bar is met; the description still adds meaningful context beyond them. The key disclosure is 'opens nothing by itself', which prevents the agent from assuming a side effect occurred, plus the follow-up path through cotlet_browser_* tools. It is consistent with the read-only annotations rather than contradicting them.

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 purpose and the 'opens nothing by itself' constraint are front-loaded effectively. The final sentence about 404s at ezlawnbiller.com/api, /developers and /docs and the QuickBooks FAQ mention is a digression from invocation guidance, and 'from ChatGPT, Claude or any AI agent' is filler that dilutes an otherwise tight 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 zero-parameter, read-only instruction-returning tool with no output schema, the description covers what comes back ('step by step – screens, buttons, fields') and what to do next. The only gap is that it never distinguishes this tool from the adjacent statement/PDF siblings, which matters given the crowded namespace.

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 nothing for the description to disambiguate and the baseline of 4 applies. The schema is fully covered and empty by design.

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 conveys what the tool actually returns – step-by-step instructions (screens, buttons, fields) for producing a pay statement PDF – rather than the PDF itself. That is a specific and non-obvious distinction from the plain name. It stops short of 5 because it never contrasts itself with the very similar sibling ez_lawn_biller_statement_pdf, so the agent cannot fully discriminate on the description alone.

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?

There is a real workflow hint: 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser', which tells the agent what to do after calling it. However there is no explicit when-to-use/when-not guidance and no routing to alternatives among the many statement/PDF siblings.

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