Twitter Api45 MCP Server

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

No annotations provided, so description carries full burden. Beyond stating it's a retrieval operation ('gets'), it lacks pagination details (despite 'cursor' parameter), rate limits, result count limits, or error behavior (e.g., private accounts).

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 efficient but front-loaded with filler ('This endpoint') and contains grammatical errors ('lates', 'it's' instead of 'its'). The errors reduce clarity despite brevity.

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?

Given the crowded tool ecosystem (numerous timeline/search variants), absence of output schema, and lack of annotations, the description should clarify what content is returned (tweets vs replies vs media) and pagination behavior. It does not.

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 has 100% coverage with examples and relationships (rest_id overwrites screenname). Description mentions screenname but adds no semantic context for 'cursor' (pagination) or 'rest_id' (internal ID format) beyond what's in the schema. Baseline 3 appropriate.

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 basic function (getting user's tweets) but contains typos ('lates', 'it's') and fails to differentiate from siblings like 'latest_replies', 'user_replies', or 'users_media'. The mention of 'endpoint' is implementation noise that doesn't help agent selection.

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 versus the 20+ sibling tools (e.g., when to prefer this over 'latest_replies' or 'search'). Does not mention if this includes retweets, replies, or media.

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