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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered; the description reinforces rather than contradicts this by stating it "opens nothing by itself". It adds genuine value beyond annotations by disclosing the output shape (step-by-step screens, buttons, fields) and the handoff to browser automation. The API research note explains why browser tools are required, though it is dated to a single point-in-time check.

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 critical clarification (it returns instructions, it opens nothing) is front-loaded in the first sentence, before the browser handoff. The final sentence about the missing official API is longer and more citation-heavy than necessary, including 404 paths, but it does justify why browser automation rather than an API path is the only route. Minor trimming would improve it.

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, annotation-covered guidance tool with no output schema, the description supplies what an agent needs: that it mutates nothing, that it returns procedural instructions, and which tool family to invoke afterward to actually perform the edit. The only gap is that it does not say what inputs or item identifiers the subsequent cotlet_browser_* calls will need, leaving the transition slightly underspecified.

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 the baseline is a 4 and there is no schema semantics for the description to compensate for. The description correctly implies a no-argument invocation by describing the call as simply returning instructions for a target item. No parameter-level ambiguity is introduced.

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 specific verb and resource ("Edit billing item") and scopes it to "the user's own EZ Lawn Biller account", then immediately clarifies that the tool itself does not perform the edit but returns step-by-step instructions. This clarification is essential and prevents misreading a mutating-sounding name as a mutating tool. It does not, however, distinguish itself from the many similar siblings such as ez_lawn_biller_edit_recurring_item or ez_lawn_biller_edit_estimate beyond the noun in the tool name.

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?

The description gives clear sequencing guidance: get the step-by-step instructions here, "then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser". That names the concrete follow-up tool family an agent should use, which is exactly the routing decision an agent needs. It stops short of stating when-not-to-use or how to choose among the many other ez_lawn_biller_edit_* siblings.

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