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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds genuinely new behavioral facts: the tool returns guidance rather than data, it opens nothing by itself, and the actual change requires a separate browser-tool step. The API note (404 on /api, /developers, /docs; QuickBooks named as the only integration) usefully explains why a browser-based path 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 operational instruction (returns steps, opens nothing, use cotlet_browser_* next) is front-loaded and compact. The trailing API-provenance sentence is longer than strictly necessary but earns some place by explaining the lack of a programmatic alternative.

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 knowledge tool with no output schema, the description supplies the workflow, the safety profile and the reason an API route is not available. The remaining gap is that an agent cannot tell from the text which exact billing-address screen or fields will be described, or whether viewing versus editing is covered.

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?

With zero parameters and 100% schema coverage, the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies no input is required.

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 (billing address in EZ Lawn Biller) and a specific output (step-by-step screens, buttons, fields), which distinguishes it from sibling tools that perform billing actions. It never says whether the 'billing address' task is viewing or editing the address, so the agent must infer the sub-task from the name alone.

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 a clear two-step flow: call this tool to get instructions, then execute with cotlet_browser_* tools in the user's Cloud Browser, and it explicitly says nothing is opened by the call itself. It does not say when to prefer this over the many billing_* siblings or what to do if the browser tools are unavailable, so there is context but no exclusions.

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