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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeat-safety profile is covered structurally. The description adds one genuinely non-structured fact — a fixed page size of 20 — plus the pagination loop, but says nothing about what a member record contains or whether ordering is stable across pages.

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?

Two short sentences, no filler, with the operation stated first and the pagination mechanic second. Every clause carries information an agent needs to call the 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?

This is a low-complexity read tool with two well-documented parameters and no output schema, and the description covers the one operational wrinkle an agent must handle — pagination with a 20-item page. It falls just short of 5 because it never characterizes the returned member objects, though with no output schema that omission is minor.

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 both parameters are already documented, including that cursor comes from the previous response's next_cursor. The description reinforces the cursor's role and contributes the page-size constant of 20, but adds no syntax, format, or edge-case detail beyond the schema; baseline 3 applies.

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 names a specific verb and resource: 'Get members of an X Community.' That is unambiguous and clearly separates it from sibling resources like get_community_moderators or get_community_tweets, though it never explicitly names a sibling it is not.

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?

Usage is implied by the resource boundary — use this to enumerate a community's membership, not its moderators or tweets — and the pagination instruction ('use cursor to paginate') is actionable. However, there is no explicit statement of when to prefer this over a sibling such as get_list_members, nor any prerequisite or exclusion.

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