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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=true, so safety is covered. The description adds genuinely new behavioral context: the tool returns procedural guidance only and performs no action, and no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; FAQ names QuickBooks as the only integration), explaining why browser automation is required.

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 workflow statement is front-loaded and useful, but the opening clause ("from ChatGPT, Claude or any AI agent") is promotional filler, and the API-provenance paragraph cites specific 404 paths and a date, which is longer than needed to convey "no public API, use the browser." The core message survives trimming.

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, no output schema and a simple read-only guidance role, the description covers what it returns and what to do next. Minor gaps remain: it does not describe the format or length of the step-by-step response, nor whether the guidance differs by report type.

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 no parameter meaning for the description to add; the baseline for a parameterless tool applies. The schema is an empty object with additionalProperties false, consistent with the description's claim that the call takes no input.

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 uses a specific resource ("Report Access") and immediately clarifies the actual output: step-by-step instructions with screens, buttons and fields rather than the data itself. It does not, however, differentiate itself from the many report-related siblings such as ez_lawn_biller_export_report or ez_lawn_biller_report_filters, which an agent could plausibly confuse it with.

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?

"Opens nothing by itself; then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser" gives a clear two-step workflow: call this for guidance, then act via browser tools. It states the context of use well but offers no explicit exclusion or comparison against the report siblings.

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