Twitter Api45 MCP Server

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

Without annotations, the description carries the full burden of disclosing behavior, yet it only implies read-only access through the verb 'get' without confirming safety or idempotency. It omits critical details such as rate limits, authentication requirements, and what data format the timeline returns.

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 description wastes words with the phrase 'With this endpoint you can' rather than starting with the action verb, failing to front-load critical information. While only one sentence, the bureaucratic phrasing reduces clarity and information density.

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 absence of annotations and output schema, the description inadequately explains what the timeline contains (e.g., tweets, replies, metadata) or how pagination behaves. A timeline retrieval tool requires disclosure of return content type and volume limits, which are missing here.

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?

The input schema has 100% description coverage, meeting the baseline threshold where the description need not duplicate parameter documentation. However, the schema descriptions only provide example values without semantic explanations, and the main description adds no clarification about what constitutes a valid list_id or 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?

The description states the tool retrieves a 'timeline of the lists,' which provides a general sense of the operation but remains ambiguous about whether it returns tweets, list updates, or other content. It fails to differentiate from sibling tools such as user_timeline or list_members, leaving the agent uncertain about the specific resource being accessed.

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?

The description provides no guidance on when to use this tool versus alternatives like user_timeline or list_members, nor does it explain pagination strategies using the cursor parameter. There are no prerequisites or conditions mentioned that would help an agent determine proper invocation context.

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