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

Annotations already indicate readOnlyHint=true, and the description adds valuable behavioral context: it details the return structure (edges[].node with fields, pageInfo, totalCount) and mentions the underlying GraphQL query ('posts'). No contradictions.

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 concise (~50 words) and front-loaded with the main action. Every sentence serves a purpose: listing, pagination, optional scoping/ordering, and return structure. No redundant or vague phrasing.

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 explains return fields, pagination parameters, and the underlying query. It could mention that limit/offset are for pagination (already in schema) and that posts are returned globally if no spaceIds, but overall it's nearly complete for a list tool without an output schema.

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 baseline is 3. The description adds limited value beyond the schema—e.g., it restates 'scope to spaces' and 'passed through as a plain string' for orderBy, but these are already in the schema descriptions.

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 'List posts across the community, with pagination'—a specific verb and resource. It distinguishes from siblings like bettermode_get_post (single post) and bettermode_list_members (different resource) by focusing on listing posts.

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 provides clear guidance on optional parameters (spaceIds, orderBy, reverse) and mentions pagination via limit/offset. It doesn't explicitly state when not to use or alternative tools, but the context is sufficient for the agent to infer usage.

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