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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds only two behavioral facts beyond that: results are cursor-paginated and it 'Returns full user objects'. It says nothing about ordering, page size, or how a partial page should be interpreted, so the added context is modest.

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 authored portion is three tight sentences with the core purpose front-loaded and the sibling routing at the end, so it reads well. It loses a point only because the injected pricing block roughly doubles the rendered length with billing boilerplate that competes with the substantive wording.

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 an output schema present, the description is not obliged to explain the returned user objects, and it correctly avoids doing so. Purpose, scope, pagination, and the alternative tool are all covered; only secondary operational detail (page size, cursor exhaustion) is absent, which is minor for a read-only list tool.

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 baseline is 3. The description's 'cursor-paginated' phrase only restates the cursor parameter's function rather than adding format or usage detail (e.g. passing back the returned cursor).

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 ('List the moderators of an X Community') plus a scope qualifier ('cursor-paginated'), and explicitly contrasts itself with the closest sibling, `get_twitter_community_members`. An agent can distinguish this from the members/info/tweets family without opening any schema.

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?

Gives an explicit use case ('identify the people who set the agenda... highest-leverage contacts for outreach or partnership') and names the alternative for a different need ('For the full membership use `get_twitter_community_members`'). Nothing about tool selection is left to inference.

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