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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningfully: it 'returns how to do it ... step by step (screens, buttons, fields) and opens nothing by itself.' That tells the agent the tool yields procedural guidance rather than data or side effects, which is not derivable from the annotations. The API-availability note further explains 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 key facts are front-loaded: what it exports, what it returns, and what to do next. The closing note about ezlawnbiller.com/api and /docs returning 404 is somewhat verbose and mid-2026 dated, but it justifies the browser-based approach and is not pure filler.

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 the return shape (screens, buttons, fields), the absence of side effects, and the follow-up tool family to use. Nothing essential is missing, though it could clarify error or fallback behavior when the account lacks customer data.

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; the schema is empty and fully specified. Baseline score of 4 applies because parameter semantics are trivially complete.

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 names a specific verb and resource ('Export customers in the user's own EZ Lawn Biller account') and the resource itself distinguishes it from sibling exports like export_items, export_payments, or export_statements. It stops short of explicitly contrasting itself with those siblings, but an agent can identify the target from the text 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?

It clearly situates the tool as the first step in a two-phase flow: get the step-by-step procedure here, 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' There is no explicit when-not-to-use guidance or named alternative for other export targets, so it stops just below the top band.

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