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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, and the description adds genuinely new behavioral context: the return value is a procedural guide, not an executed action, which explains why a nominally destructive-sounding operation is marked read-only. It also discloses the absence of a public API (404s on /api, /developers, /docs; QuickBooks named as the only integration), justifying the browser-automation route. It does not say what happens if the template is missing or already archived.

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?

Front-loaded with the action and the key constraint (returns steps, opens nothing), so an agent gets the critical facts first. The trailing API-availability sentence is somewhat long and evidentiary in tone but does earn its place by explaining why browser tools are required.

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 full annotation coverage, the definition supplies everything needed to call it correctly: what it does, what it returns, and what to do next. The remaining gap is minor—no mention of failure modes or what the guide looks like if the template name is ambiguous.

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 and has no input fields to misinterpret, which is the baseline-4 case. The description correctly implies no inputs are needed by describing the call as a lookup of steps rather than a parameterized action.

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 verb and resource ("Archive template in the user's own EZ Lawn Biller account") and clarifies that the tool returns instructions rather than performing the archive, which separates it from the sibling edit/new template tools by action type. It stops short of explicitly contrasting itself with ez_lawn_biller_edit_template or new_template, so a 4 rather than a 5.

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 operational path: call this to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Cloud Browser. It also warns that the tool "opens nothing by itself," preventing an agent from assuming the archive already happened. No explicit when-not-to-use or named alternative guidance is given.

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