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

Annotations already convey readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond annotations: cursor-based pagination and a full-user-object return shape. It stops short of discussing limits or cursor lifecycle, but the annotations lower the bar for safety-related disclosure.

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 with no wasted words: purpose is first, use case follows, return shape is stated, and the relevant alternative is named. Every sentence contributes actionable information.

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 simple list operation with a required ID, an optional cursor, a full output schema, and safety annotations, the description covers all essential decision points: what it lists, why to use it, what it returns, and which sibling handles the related moderator case.

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 description coverage is 100%, so both `community_id` and `cursor` are already documented in the schema. The description adds only a minor nod to pagination via 'cursor-paginated' but no extra meaning beyond the schema, warranting the baseline score of 3.

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 ('List') with a precise resource ('members of an X Community') and states it is cursor-paginated. It also distinguishes itself from the moderators tool, so an agent can tell them apart immediately.

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 explains when to use this tool: to map participants in a topic-specific group, noting that membership is opt-in and higher-signal than general followers. It explicitly points to `get_twitter_community_moderators` for the moderator subset, giving clear routing to an alternative.

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