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

Annotations declare readOnlyHint=true and idempotentHint=true; the description is consistent and adds real context beyond them — it explains that nothing is opened or changed by the call itself and that the actual change happens through separate browser tools. It also justifies why it works this way (no public API), which an agent otherwise would not know.

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 and purposeful in its first sentence and the browser-tool handoff, but the closing API-provenance sentence (404 results for /api, /developers, /docs, FAQ mentions QuickBooks) is lengthy justification that does not help the agent call the tool correctly and dilutes the operative instructions.

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 output schema, the description correctly covers what is returned (screens, buttons, fields) and the follow-up mechanism, which is the important part. However, for a tool that is supposed to 'edit a recurring item', the lack of any way to identify the target item and the absence of guidance on what the agent should supply in its prompt leaves a meaningful gap.

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 baseline for a 0-parameter tool applies. The description does not explain how the agent indicates which recurring item is meant, but since the schema allows no such input, that is a design property rather than a missing description element.

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+resource (edit a recurring item in the user's own EZ Lawn Biller account) and immediately clarifies the actual output: step-by-step instructions rather than a performed edit. It does not differentiate from the near-identical sibling ez_lawn_biller_edit_recurring_billing, so it falls short of 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?

Tells the agent what to do after calling ('then do it with the cotlet_browser_* tools in the user's ... Cloud Browser'), which is useful sequencing guidance. It gives no condition for choosing this over the many similarly named edit/recurring siblings, so the when-to-use part is only implied.

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