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

Annotations already establish that this is a safe read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: most-recent-first ordering, the fields returned, and how pagination works.

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 front-loaded with the inbox value proposition, then covers listing scope, return fields, filtering, and pagination without wasted text. It is appropriately sized for a three-parameter list tool.

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?

There is no output schema, but the description sufficiently explains the returned fields, ordering, filtering, and pagination required to call and interpret the tool. Annotations cover the safety profile, so the description is complete for this read-only list operation.

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%, so the schema already documents all three parameters. The description still adds practical meaning for unread_only and cursor, especially by clarifying that the next cursor is passed back as cursor for the next page.

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 uses a specific verb-resource pairing: it lists Skool Chat conversations across all groups, most recent first, and names the returned fields. This clearly distinguishes it from single-conversation and messaging siblings such as get_conversation and send_message.

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 clear usage context as the Skool Chat inbox and explains when to use unread_only to focus on conversations needing an answer. It also explains pagination via cursor, though it does not explicitly name alternatives or exclusions.

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