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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself', which is the single most valuable disclosure for a tool whose name sounds mutating. It also explains why browser automation is required (no public API, FAQ/manual only names QuickBooks), adding real context beyond the annotations. It does not describe the shape of the returned steps in detail.

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 clarification (returns instructions, opens nothing) is front-loaded, and the API-availability note earns its place by justifying the browser-based path. The final sentence about 404s on /api, /developers and /docs is somewhat verbose for a tool description but is defensible as rationale.

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 output schema, the description carries the burden of explaining returns and does so ('how to do it step by step — screens, buttons, fields'). Combined with the handoff to browser tools, an agent has enough to call it and use the result correctly; only finer detail about the returned format is missing.

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 the baseline is a 4. The description correctly implies no input is needed — the target account and task are implicit — and introduces no confusion about arguments.

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 action and resource (extend validity in the user's own EZ Lawn Biller account) and clarifies the crucial nuance that it returns step-by-step instructions rather than performing the change. It also names the cotlet_browser_* tools that actually carry out the work, so the agent can separate this from real mutation tools without opening a schema.

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 a clear two-step workflow: call this to get the screens/buttons/fields, then act via the browser tools. It does not state explicit exclusions (e.g., when not to bother with the guide), but the sequencing guidance is unambiguous and actionable.

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