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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false; the description adds genuinely non-redundant behavior — that no browser action is performed by the tool itself and that the return value is a procedural guide (screens, buttons, fields). The API-limitation note adds decision-relevant context. It does not describe how large or structured the returned guide is, which keeps it at 4.

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 critical qualifier ('opens nothing by itself') is placed mid-sentence in a long second sentence rather than front-loaded, which risks an agent skimming past it. The closing sentence about Patreon's official API v2 is tangential to invoking this specific tool and reads as shared boilerplate. The content is largely useful but not tightly structured.

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, read-only guide tool with no output schema, the description covers what an agent needs: what it returns, that it has no side effects, and what to do next. The only gap is that the shape of the returned instructions is only loosely characterized, but that is minor given the tool's simplicity.

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 and the schema is fully described, so there is no parameter meaning the description needs to supply. Baseline 4 applies; nothing here adds or obscures parameter semantics.

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 (members of the user's own Patreon account) and clarifies the actual mechanic: it returns step-by-step instructions rather than data, and 'opens nothing by itself.' That correction is valuable because the name/title ('List members') would otherwise imply it returns a member list. It falls short of 5 only because the opening sentence still reads as if the tool performs the listing before the second sentence reverses that expectation.

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 follow-on path: run this first, then execute the steps with the cotlet_browser_* tools in the user's Patreon Cloud Browser. It also implicitly excludes relying on Patreon's public API for this task by noting the API cannot create posts, message members, or edit tiers. There is no explicit 'do not use this when...' clause, so it stops short of full routing guidance.

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