Twitter Api45 MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. It does not clarify that this is a read-only operation, does not explain pagination behavior (despite the cursor parameter), and omits any mention of rate limits, auth requirements, or return value structure.

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?

At six words, the description is efficiently structured without waste, but it is underspecified rather than appropriately concise. Given the lack of annotations and output schema, additional sentences explaining usage and behavior would be warranted.

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?

Without an output schema or annotations, the description should explain what member data is returned and how pagination works. It lacks differentiation from similar sibling tools and provides no context about community membership semantics (e.g., public vs. private communities, moderation status).

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%, providing examples for both community_id and cursor. The description adds no semantic meaning beyond the schema baseline, nor does it explain the cursor's role in pagination or the expected format of the community_id beyond the example given.

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 'Gets the list of community members' is essentially a tautology that converts the tool name into a verb phrase without adding specificity. It fails to distinguish from sibling tool 'list_members' or clarify what constitutes a 'community' in this context (X/Twitter communities vs. other groupings).

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?

No guidance provided on when to use this versus 'list_members' or other community-related tools. No mention of prerequisites (e.g., valid community_id format) or pagination workflow despite the cursor parameter implying pagination is required for large result sets.

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