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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the most-recent-first ordering, the shape of each row, and the auth prerequisite (Cotlet API key with access to this app). Rate limits and pagination behavior remain undisclosed.

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?

Purpose is front-loaded, but the returned fields are stated twice ("who, unread count and last message preview" then again as "the other person, unread count and a preview of the last message"), which is redundant filler for such a short description.

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 usefully describes the return shape and ordering, and it covers the auth requirement. For a simple read-only list with 100% schema coverage, this is nearly complete; only pagination and scope limits are left unaddressed.

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% (limit, cursor, unread_only all documented). The description reinforces unread_only's intent ("what needs an answer") but adds nothing about limit or cursor beyond the schema. Baseline 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?

States a specific verb and resource ("Lists your Skool Chat conversations") and even enumerates the returned fields (other person, unread count, last message preview). It is clearly distinct from a single-conversation getter, though it never names a sibling tool to sharpen the boundary.

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?

"Set unread_only to see only what needs an answer" gives functional guidance for one parameter, but there is no explicit when-to-use versus skool_get_conversation or skool_send_message, and no when-not guidance. Usage is only implied.

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