twitterapi-io-mcp

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

With no annotations provided, the description carries full burden. It effectively discloses key behavioral traits: it searches documentation (not the API itself), returns ranked results with relevance scores, and supports specific query formats (camelCase, underscore). However, it doesn't mention rate limits, authentication requirements, or pagination behavior, which would be useful for a search tool.

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 well-structured with clear sections: purpose statement, usage guidelines, return values, and examples. Every sentence earns its place by providing specific guidance or examples. The front-loaded purpose statement immediately communicates the tool's function.

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 an output schema (so return values are documented elsewhere) and 100% schema description coverage, the description provides excellent contextual completeness. It covers purpose, usage guidelines, behavioral context, and examples - everything needed for an agent to understand when and how to use this search tool effectively.

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%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema - it provides example queries but doesn't explain parameter semantics beyond what's in the schema descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 searches TwitterAPI.io documentation for API endpoints, guides, and blog posts. It specifies the exact scope ('entire documentation') and distinguishes from siblings by being a comprehensive search tool rather than fetching specific resources like get_twitterapi_endpoint or list_twitterapi_endpoints.

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 includes an explicit 'USE THIS WHEN' section stating 'when you need to find information across the entire documentation.' This provides clear guidance on when to use this tool versus its siblings, which appear to fetch specific documentation components rather than performing comprehensive searches.

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