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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so 'opens nothing by itself' is largely confirmatory. The description nevertheless adds real behavioral information no annotation carries: the return value is procedural instructions (screens, buttons, fields) rather than data, and follow-up requires the separate cotlet_browser_* tool family.

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 purpose and the two-stage workflow are front-loaded in the first two sentences, and each earns its place. The trailing API-availability sentence ('404 on /api, /developers, /docs...') is account-level trivia that does not help an agent decide or invoke this specific tool.

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, non-destructive guidance tool with no output schema, the description supplies the essential missing piece: what actually comes back (step-by-step instructions) and what to do next (cotlet_browser_* tools). It does not describe failure modes or how verbose the returned steps are, but that gap is minor at this complexity.

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 with an empty, closed schema (additionalProperties: false), so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter-level gaps exist.

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 opening line ('Customer list in the user's own EZ Lawn Biller account') largely restates the name and title, and reads as if the tool returns customer data. Only the second sentence clarifies the real function: 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields).' The actual purpose is stated, but the leading framing creates a mismatch with what the tool returns, and no sibling (e.g. ez_lawn_biller_customer_search) is named to disambiguate.

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 gives clear orchestration guidance — 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser' — which tells the agent this is a first step in a two-stage workflow. However, it offers no guidance on when to pick this over the many customer-related siblings, and no explicit when-not condition.

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