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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the tool performs no action in the account, it returns a step-by-step procedure referencing screens/buttons/fields, and the actual change must be done through separate browser tools. That is useful context beyond the annotations.

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 and the follow-up workflow are front-loaded in the first two sentences, which are tight and earn their place. The final sentence about the missing public API is supporting rationale for using the browser tools, but it is verbose and reads as boilerplate appended to every tool in this family.

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 parameters, no output schema, and a full set of annotations, the description covers what the agent needs: what it returns, what it does not do, and what to call next. The only shortfall is the absence of an explicit hand-off to the named sibling tools rather than the generic cotlet_browser_* reference.

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 there is nothing for the description to disambiguate; the empty schema is fully consistent with a parameterless guidance call. Baseline for a 0-param tool is 4.

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 states a specific resource (statement) and clarifies the surprising mechanic: it "returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself." That distinguishes it from an execution tool, though it never names the concrete execution sibling (e.g. ez_lawn_biller_statement_run) to sharpen the contrast.

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 sequencing guidance ("then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser"), which implies this is a first step in a two-stage workflow. However, it never states when to skip this tool and call statement_run or statement_preview directly, so the choice among siblings is left to inference.

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