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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing that it 'opens nothing by itself' and by describing the return content (step-by-step screens, buttons, fields), which the annotations cannot convey. The trailing 'Recurly's official API: Yes...' sentence is context but adds no behavioral clarity for invocation.

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 key behavior (returns instructions, opens nothing) is front-loaded, but the opening clause 'from ChatGPT, Claude or any AI agent' is marketing filler and the API-availability sentence is irrelevant to invoking the tool. Trimming those would sharpen an otherwise short description.

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 guide tool with no output schema, the description covers what it returns and what the agent should do next. It leaves open whether a Cloud Browser session must already be open before calling, which would be useful given the two-step workflow it describes.

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 there is nothing for the description to disambiguate. The baseline for a parameterless tool is 4, and the description does not create confusion about inputs.

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 the resource (past-due accounts in the user's own Recurly account) and, crucially, corrects the misleading name/title by stating it returns step-by-step instructions (screens, buttons, fields) rather than the data itself. An agent can tell it produces a guide, not a listing. It stops short of contrasting against the recurly_* action siblings beyond the generic cotlet_browser_* handoff.

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 workflow: get the steps here, then execute them with the cotlet_browser_* tools in the Recurly Cloud Browser. That is clear context for when to call it. It does not state exclusions or when to prefer recurly_find_account or the other recurly_* tools instead.

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