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 safety profile is covered. The description adds genuinely new behavioral context: the call is a no-op in the target app and only yields instructions, which must then be executed through cotlet_browser_* tools. The API-availability note also explains why a browser-driven recipe exists, though it is more justification than behavior.

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 is front-loaded in the first two clauses, which is good. The trailing sentence about 404s on /api, /developers and /docs plus QuickBooks being the only named integration is verbose supporting evidence that could be condensed to a short phrase without losing meaning.

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 explaining what comes back, and it does so generically ('step by step (screens, buttons, fields)'). It does not indicate how granular or long the returned guide is, nor that no account data is returned, leaving the agent to discover the response shape on first call.

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; baseline 4 applies. The description correctly implies no inputs are needed because the output is generic guidance rather than an account-specific operation.

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?

Despite a name that suggests it produces a PDF, the description makes clear it returns step-by-step EZ Lawn Biller instructions ('screens, buttons, fields') and 'opens nothing by itself.' That is a specific, non-obvious purpose an agent can act on. It stops short of distinguishing itself by name from close siblings such as statement_preview or download_pdf.

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 implies usage context (an AI agent wanting a Statement PDF) and states the required follow-up: perform the actions with cotlet_browser_* tools in the user's Cloud Browser. It gives no exclusions or explicit alternatives among the many statement_* and *_pdf siblings, so the agent must infer which of them to pick.

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