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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false; the description reinforces this by stating explicitly that it 'opens nothing by itself', which prevents the agent from assuming the send happens server-side. The note that no public EZ Lawn Biller API exists explains why browser automation is required. It does not describe what the returned instructions look like in structure (e.g. a single blob vs numbered steps per screen), but the core behavioral surprise is covered.

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 correction (returns instructions, does not open anything) is front-loaded in the second sentence, ahead of the browser-tool follow-up. The closing API-availability sentence with specific 404 paths and dates is slightly over-detailed but does justify the browser-based approach. No filler beyond that.

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 and no output schema, the description carries the burden of telling the agent what comes back, and it does: step-by-step screens, buttons and fields, scoped to the user's own account. It is complete enough to call correctly, though it leaves open whether the returned steps must be confirmed with the user before executing them.

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 no parameter semantics to disambiguate and the schema is trivially complete. The description correctly implies no arguments are needed by describing a fixed, account-scoped procedure. Baseline for a no-parameter tool applies.

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 verb and resource (send next month's statements) and immediately clarifies the actual mechanism: it returns step-by-step how-to instructions rather than performing the send. That distinction separates it from the name's apparent action semantics. It stops short of naming which sibling sending tool (e.g. ez_lawn_biller_send_statement, ez_lawn_biller_email_all_statements) handles adjacent cases, so differentiation is only partial.

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?

Clear workflow context: this tool yields the procedure, then the agent executes it with cotlet_browser_* tools in the user's Cloud Browser. It also implicitly scopes usage to 'next month's statements' rather than current-period statements. It does not say when a sibling like ez_lawn_biller_send_statement or ez_lawn_biller_statements would be the better choice.

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