twitterapi-docs-mcp

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

With no annotations provided, the description carries the full burden. It discloses the tool's behavior by specifying what information it returns (pricing tiers, credit costs, QPS limits) and implies it's a read-only operation. However, it doesn't mention potential rate limits of this tool itself or authentication requirements.

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 is perfectly structured with three distinct sections: purpose statement, usage guidelines, and return information. Each sentence earns its place with zero wasted words, and the information is front-loaded appropriately.

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 tool has no parameters, has an output schema (so return values don't need explanation), and the description comprehensively covers purpose, usage context, and behavioral aspects, this description is complete for a simple information retrieval 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?

The tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist. It provides context about what information will be retrieved, which adds value beyond the empty schema.

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 clearly states the tool's purpose with specific verbs and resources: 'Get TwitterAPI.io pricing information' followed by detailed scope ('credit system, endpoint costs, QPS limits'). It distinguishes from siblings like get_twitterapi_endpoint (endpoint details) and get_twitterapi_auth (authentication).

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 'USE THIS WHEN' section explicitly states when to use this tool: 'when you need to know API costs, credit calculations, or rate limits.' This provides clear context and distinguishes it from alternatives like searching docs or listing endpoints.

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