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

The readOnly/idempotent/non-destructive annotations already cover the safety profile, but the description adds genuine value by stating it 'opens nothing by itself' — pre-empting the wrong assumption that it navigates the browser. However, the closing sentence about Recurly's official REST API is noise that could mislead an agent into thinking this tool calls that API, and nothing is said about the guide's scope limits or freshness.

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 workflow is front-loaded and the core two sentences are tight. The third sentence about Recurly's REST API and a 'checked 14 Oct 2026' verification date does not help the agent call this tool and should be cut.

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, no-output-schema guide tool, the description covers what is needed: what it returns (steps naming screens, buttons, fields), what it does not do (opens nothing), and which tool family performs the action. Only the confusing API aside keeps it from being fully complete.

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 baseline-4 case; there is nothing for the description to disambiguate. It does at least imply the target (the user's own Recurly account/session), which is the only implicit 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 specifies a concrete goal (finding an account in Recurly) and, crucially, discloses that the tool 'Returns how to do it in Recurly step by step (screens, buttons, fields) and opens nothing by itself' — i.e. it is a how-to guide, not an executor. That clarification rescues what would otherwise be a misleading 'find' name. It still blurs slightly with cotlet_app_guide and with data-returning siblings like recurly_list_past_due_accounts, since 'find account' could be read as retrieving account data.

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 an explicit two-step workflow: get the step-by-step here, then 'do it with the cotlet_browser_* tools in the user's Recurly Cloud Browser.' That tells the agent both when to call this and what to call next. It stops short of stating when NOT to use it (e.g. when the user wants account data rather than UI navigation).

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