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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them ('opens nothing by itself'). It adds real context beyond the annotations: the output is a UI walkthrough of screens, buttons and fields, plus the justification that Skool has no public API or developer docs. It stops short of saying whether the guide is generated fresh, account-specific, or static.

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 disclosure ('returns how to do it step by step ... opens nothing by itself') is buried in the second sentence, behind a first sentence padded with 'from ChatGPT, Claude or any AI agent'. The dated parenthetical 'checked 10 Oct 2026' is fine as provenance but adds length without changing agent behavior.

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 must convey the return payload, and it does outline it (step-by-step screens, buttons, fields). However, with zero parameters it is unclear how the tool scopes to a particular Skool group or whether the user's browser session must already be authenticated, which are gaps for a browser-driven workflow.

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 closed, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no arguments are needed because it only returns a procedure.

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 states a concrete resource (members in the user's own Skool account) and then importantly redefines the actual behavior: it returns step-by-step instructions rather than data, and 'opens nothing by itself'. That is a specific, unambiguous statement of what the tool does. It loses a point because the opening sentence reads as if it performs the listing, and it never distinguishes itself from the sibling tool named `list_members`, which an agent would likely assume does the same thing.

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 a follow-on workflow ('then do it with the cotlet_browser_* tools in the user's Skool Cloud Browser'), which tells the agent how to act on the output. But it never says when to pick this over `list_members` or `search_members`, which are the obvious alternative paths for the same resource. Usage is implied rather than stated.

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