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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, and the description reinforces this with "opens nothing by itself," so the safety profile is unambiguous. It adds genuinely useful context beyond annotations by documenting that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks is the only named integration), which explains why browser automation is required.

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 guidance is front-loaded, but the sentences are long and run together with semicolons, and the API-availability research reads as a tangent appended to the same paragraph. It is informative rather than padded, but the final paragraph could be condensed to a single clause about using the browser tools because no public API exists.

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 no-parameter, no-output-schema instruction tool, the definition covers what the call returns (step-by-step screens, buttons, fields) and what to do next. The only meaningful gap is failure handling — what the agent should do if the user has not yet set up a Cloud Browser session.

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, which is the correct baseline for a pure instruction-returning tool. No parameter meaning is needed, and the description correctly implies the call needs no input.

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 makes clear this is a guidance/knowledge tool: it "Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself." That verb+resource is specific enough to distinguish it from action siblings, though the opening phrase "Sync status" is a bare noun that momentarily reads like a status-check tool rather than a how-to.

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 states the intended workflow explicitly: call this to get the steps, then "do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." It also rules out a side effect ("opens nothing by itself"). What is missing is routing against plausible siblings such as ez_lawn_biller_auto_sync, which an agent would have to disambiguate on its own.

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