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

Annotations already declare readOnly, non-destructive, idempotent and closed-world, so the safety profile is covered. The description adds genuine value beyond that: it discloses the return content ('step by step (screens, buttons, fields)') and that no action is performed, which an agent cannot infer from the empty schema. The API-availability note further 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 behavior is described efficiently, but the final third is a long evidentiary note about 404s on /api, /developers and /docs plus a QuickBooks mention. That investigation history explains motivation but does not help an agent choose or invoke the tool, and the framing sentence 'from ChatGPT, Claude or any AI agent' is filler.

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 carries the burden of describing the return value and does so concretely ('screens, buttons, fields'). For a zero-parameter, read-only guidance tool this covers what an agent needs to invoke it and use the result, though it could say more about how detailed the returned procedure is.

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 4 and there is nothing for the description to document. The description correctly signals there is no input to supply.

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 second sentence states precisely what the tool does: it returns step-by-step instructions (screens, buttons, fields) rather than performing the subscription. The opening phrase 'Visit report subscription in the user's own account' restates the name and is momentarily ambiguous, but is immediately disambiguated by 'opens nothing by itself'. It doesn't explicitly differentiate against near siblings such as ez_lawn_biller_visit_report_settings or ez_lawn_biller_send_visit_report.

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?

Clearly signals the intended workflow: call this to learn the procedure, then act with the cotlet_browser_* tools in the user's Cloud Browser. The 'opens nothing by itself' caveat prevents misuse as a mutation tool. It does not name when to prefer the sibling configuration/report tools instead, so it is clear context without exclusions.

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