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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with them ('opens nothing by itself'). It adds real context beyond the annotations: that the output is a procedural walkthrough of screens/buttons/fields, and that the actual mutation must happen through a separate browser-automation tool set.

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 critical fact — that this tool only returns instructions and performs nothing — is buried mid-sentence after the framing clause, and filler like 'from ChatGPT, Claude or any AI agent' earns no place. The closing API-availability paragraph (404s on 11 Nov 2026, QuickBooks-only integration) is long but does justify why browser automation is the only path, so it is defensible rather than pure padding.

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 definition covers what the agent needs: what comes back (step-by-step screens, buttons, fields), what it does not do, and which tools to use next. Only the exact shape of the returned instructions remains unspecified, which is minor here.

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 input schema is an empty object with additionalProperties=false, so there are no parameters whose meaning needs explanation. The description adds nothing about inputs because there is nothing to add, which is the expected baseline for a zero-parameter tool.

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 the resource (an order in the user's own EZ Lawn Biller account) and, critically, corrects the misleading verb by stating it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from real action tools, though it never contrasts with the sibling ez_lawn_biller_gateway_order or other order-mutating tools.

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 gives a clear next step: use the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser to actually perform the change. It does not state when NOT to use it or which sibling to pick for an order action, so the routing guidance is one-directional rather than complete.

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