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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true; the description adds genuinely non-redundant behavior by stating the tool returns step-by-step UI instructions and 'opens nothing by itself,' which resolves the apparent tension between the name 'edit_template' and a read-only annotation. It also explains why browser automation is required (no public API found; ezlawnbiller.com/api, /developers and /docs returned 404, QuickBooks named as the only integration). It does not describe the shape/length of the returned step-by-step content, so it is not fully complete on the behavioral side.

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 mechanic is stated early and clearly, but the opening 'from ChatGPT, Claude or any AI agent' is promotional filler, and the API-availability sentence spends a lot of words on 404 results that could be compressed to 'no public API; browser automation required.' Still readable and reasonably front-loaded.

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 tool with no output schema, the description covers what an agent most needs: what comes back (step-by-step screens/buttons/fields), that no state changes, and which tool family to use next. It lacks prerequisites for the Cloud Browser session and any indication of how the instructions are scoped to a specific template, which is a minor gap given the tool's simplicity.

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 has zero parameters and additionalProperties is false, so there is nothing for the description to disambiguate. The description correctly implies no arguments are needed and does not invent any. Baseline 4 applies for a no-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 a concrete verb+resource (edit a template in EZ Lawn Biller) and then discloses the actual mechanic: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That tells an agent this is a procedural-guidance tool rather than a mutator, which is the key distinction from the surrounding edit_* siblings. It stops short of explicitly differentiating itself from ez_lawn_biller_new_template or ez_lawn_biller_archive_template, so it is clear but not sibling-differentiated.

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?

Usage is implied by the two-step flow: call this first to get instructions, 'then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' That is a real routing hint toward an alternative tool family. However, it never states the conditions that select this tool over sibling edit tools (e.g. editing an existing template vs creating or archiving one), so the when-to-use guidance remains implicit.

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