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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: it explains the return is procedural guidance (screens, buttons, fields), that invoking it performs no action in the account, and that a separate browser tool is needed to actually execute the steps. The documented absence of a public API preempts an agent from searching for an API path.

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 operational point (returns steps, opens nothing, use the browser tools) is present but sits behind a title-restating first sentence. The API-availability note is useful context but is written as a verbose investigative aside rather than a tight statement.

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 and rich annotations, the description covers what comes back and what to do next. It does not say how the returned steps are scoped (e.g., does it cover creating, editing, deleting templates) or how to pick among the several template siblings, leaving a gap for an agent navigating this catalog.

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 no parameters and the schema is an empty closed object, so there is nothing for the description to clarify. Baseline 4 applies; the description correctly implies no input is required.

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 eventually states that it returns step-by-step instructions (screens, buttons, fields) for setting up custom templates, and clarifies that it 'opens nothing by itself.' However, the opening sentence ('Custom templates in the user's own EZ Lawn Biller account...') restates the title rather than naming a verb, so an agent must read to the second sentence to learn this is a read-only how-to lookup. It also does not distinguish itself from siblings like ez_lawn_biller_templates or ez_lawn_biller_notice_templates.

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 follow-up path: use the cotlet_browser_* tools in the Cloud Browser after getting the steps. But it offers no condition for choosing this over the other template-related siblings (templates, notice_templates, archive_template, custom_role), and no when-not-to-use guidance.

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