skool_posts_list

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

With no annotations available, the description carries the behavioral disclosure burden. It clearly communicates a read-only list operation, explicitly identifies the response contents (title, preview, author, likes, comment count), and notes pagination support. It stops short of mentioning auth requirements or pagination response structure, but for a simple list tool this is adequate.

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?

Three sentences, each with a distinct job: state the operation, state filtering/pagination, and state the returned fields. There is no filler, repetition, or unnecessary elaboration.

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 read-only list tool with four documented optional parameters and no output schema, the description plus input schema covers what the tool does, how to filter and page, and what response fields to expect. Nothing essential is missing for an agent to invoke it correctly.

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?

Schema coverage is 100% and every parameter already has a descriptive comment: page is 1-based, sort defines enum meanings, category is a UUID, and community is a slug with a config default. The description's mention of filtering and pagination adds no semantic detail beyond the schema, so it stays at the baseline.

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 opens with a specific verb and resource: 'List posts in a community feed.' It adds scope with filtering and pagination and enumerates the returned fields, which clearly distinguishes it from sibling tools like skool_posts_get, skool_posts_create, and skool_posts_comment.

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?

The description implies when to call the tool — whenever a post feed listing with optional filtering is needed — but it provides no explicit guidance about when to prefer it over alternatives such as skool_posts_get for full post details, or when not to use it.

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