skool_members_list

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

The description discloses pagination behavior and the type of member info returned, which is useful. However, it does not clarify that this likely lists only active/approved members (given the sibling skool_members_pending), and there are no annotations to rely on for safety or scope.

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 description is two concise sentences, front-loaded with the primary action ('List community members') and includes essential return info. There is no unnecessary wording.

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?

The description gives basic context (pagination, return fields) but omits details about pagination behavior (e.g., page size, response structure) and does not clarify the scope relative to pending members. Since there is no output schema, this leaves some ambiguity for the agent.

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 input schema covers 100% of parameters with clear descriptions (page, community). The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool lists community members with pagination and shows the returned fields (name, bio, role, online status). It names a specific verb and resource, but does not explicitly differentiate from the sibling skool_members_pending, so it's not a perfect 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?

No guidance is provided on when to use this tool versus alternatives like skool_members_pending. The description only explains what the tool does, not when it should be chosen.

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