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

Annotations only say readOnly/idempotent/non-destructive; the description adds the crucial fact that this tool "opens nothing by itself" and returns a procedural walkthrough covering screens, buttons and fields. It also discloses the negative API research result with dated evidence, which explains the browser-automation dependency. This is context an agent could not obtain from the annotations, schema, or sibling names.

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?

Front-loaded with what it does and the key caveat that it performs no side effects, both in the first two clauses. The trailing API-research sentence is the longest element and reads as justification rather than instruction, but it earns its place by explaining the browser-tool handoff.

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 and strong annotations, the description covers what is returned (step-by-step screens, buttons, fields) and what to do next. The one remaining gap is that it never says how the target visit/report is identified, which matters because there are no input parameters.

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 is 4. It could have noted that visit/report selection happens later in the browser flow rather than at call time, but no schema exists to misread.

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 ("Send visit report in the user's own EZ Lawn Biller account") and immediately clarifies the actual mechanics: it returns step-by-step instructions rather than performing the send. That resolves the ambiguity in the tool name. It does not explicitly distinguish itself from nearby siblings like ez_lawn_biller_service_visit_reports or ez_lawn_biller_send_email, so it stops short of a 5.

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?

Gives clear operational routing: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. It also explains why no direct API path exists (404s on /api, /developers, /docs; QuickBooks named as the only integration). It does not state when to prefer a sibling tool such as ez_lawn_biller_service_visit_reports instead.

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