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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this by stating explicitly that nothing is opened or changed, and that execution requires separate browser tools. It also explains the environmental constraint (no public EZ Lawn Biller API found, 404s on /api, /developers, /docs, QuickBooks the only documented integration), which justifies the browser-automation path. It stops short of describing output shape or auth requirements 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 core behavior is front-loaded in a dense run-on sentence, which is good, but the trailing API-investigation note is verbose—listing three 404 URLs, a date, and the QuickBooks detail—and dilutes the actionable content. Some of that evidence could be compressed to a clause.

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 zero parameters, no output schema, and strong annotations, the description carries the remaining burden and largely meets it: it explains what the return value is (a step-by-step guide), that the tool is inert, and how to act on the result. An agent has enough to call it correctly and chain the follow-up.

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 schema is an empty object with 100% coverage, so there are no parameters whose meaning needs explaining. The description correctly implies a parameterless call; nothing more is required here.

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 makes the critical distinction that this tool does not create anything but returns step-by-step instructions (screens, buttons, fields) for creating a new template, which disambiguates the misleading 'new_template' name. It names the browser tool family (cotlet_browser_*) as the actual actor, though it never contrasts itself with siblings like ez_lawn_biller_edit_template or ez_lawn_biller_archive_template.

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 usage sequence: call this to get the walkthrough, then execute it with cotlet_browser_* in the user's EZ Lawn Biller Cloud Browser. It states the tool 'opens nothing by itself,' which implicitly excludes it from direct action. No explicit when-not conditions are given beyond that.

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