Twitter Api45 MCP Server

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

With no annotations provided, the description carries full burden but discloses almost nothing: no mention that cursor controls pagination, no explanation of ranking behavior, no rate limits, and no description of what the returned posts contain.

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?

Single sentence is appropriately brief, but it is under-informative rather than efficiently dense. The brevity results from omission of critical details rather than disciplined editing.

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?

Inadequate for a 3-parameter tool involving pagination. Missing: differentiation from sibling search tools, explanation of cursor-based pagination, ranking options, and return structure (no output schema to compensate).

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?

While schema has 100% coverage, the descriptions are only example values ('Example value: 1783990533192651232') without semantic meaning. The description adds no context for what cursor (pagination) or ranking (sort order) actually do, leaving the agent to guess their purpose.

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 the basic action (returns posts) and resource (community), but lacks specificity regarding which community (requires ID) and fails to differentiate from sibling search tools like communities_posts_search_latest or communities_posts_search_top.

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?

Provides no guidance on when to use this tool versus the search alternatives (communities_posts_search_latest/top), no mention of pagination workflows, and no prerequisites (e.g., needing to obtain community_id first).

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