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 non-obvious behavior beyond that: the tool performs no action itself, returns screen/button/field instructions, and hands execution to a separate cotlet_browser_* toolset. It does not cover prerequisites such as being signed in to the account.

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 hand-off to browser tools are front-loaded in the first sentence. The trailing API-availability note (404s on /api, /developers, /docs; QuickBooks as the only integration) is long but earns its place by explaining why UI-driving browser tools are needed. It is a single sprawling sentence rather than cleanly segmented, which costs a point.

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 it returns (step-by-step screens, buttons, fields) and what it does not do (it opens nothing). The remaining gap is that it never defines what a "notice exception" is or what account state the user must be in, but the essentials for correct invocation are present.

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 closed (additionalProperties=false), so there is nothing to disambiguate. Baseline of 4 applies; the description correctly implies no input is required.

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?

States a specific verb and resource ("Print notice exceptions in the user's own EZ Lawn Biller account") and immediately clarifies the actual output is step-by-step instructions rather than a print action. It does not explicitly differentiate itself from close siblings such as ez_lawn_biller_notice_preview or ez_lawn_biller_print_all, and "notice exceptions" remains somewhat jargon-y without definition.

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 does route the agent onward ("then do it with the cotlet_browser_* tools") and warns that this tool "opens nothing by itself," which is genuine usage guidance. However, it never states when to choose this over notice_preview, notice_dry_run, or print_all, so the alternative selection is left to inference.

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