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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety bar is lower. The description still adds real behavioral context beyond them: nothing is opened or mutated ('opens nothing by itself') and the return value is a sequence of screens, buttons and fields the agent must then replay via browser tools. The note that Ghost ships a REST Admin API but no official MCP server 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 purpose and the crucial 'opens nothing by itself' caveat are front-loaded, which is good. However the opening 'from ChatGPT, Claude or any AI agent' is filler, and the closing sentence about Ghost's official REST Admin API and the 'checked 17 Oct 2026' date is tangential justification that does not help an agent decide or invoke.

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 tool with no output schema, the description covers the two things an agent needs: what comes back (step-by-step UI instructions) and what to do next (cotlet_browser_* tools). It leaves the exact shape of the returned instructions implicit, but given the tool's simplicity that gap is minor.

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 (schema coverage 100%), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level detail is needed or missing.

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 a specific verb and resource ('List members in the user's own Ghost account') and clarifies the unusual deliverable: it returns step-by-step Ghost UI instructions rather than the member list itself ('opens nothing by itself'). That distinguishes it from the cotlet_browser_* siblings that actually perform the listing, though the name 'ghost_list_members' and the actual output still sit at slight odds, which keeps it from a 5.

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 states a workflow: call this to get the how-to, 'then do it with the cotlet_browser_* tools in the user's Ghost Cloud Browser.' That is clear routing guidance to the alternative execution path. It does not address when to prefer this over Ghost-adjacent siblings like ghost_label_members or when not to use it at all.

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