list_twitterapi_endpoints

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 that the tool lists endpoints 'organized by category' and returns 'Endpoint names with HTTP method and path for each category', which adds useful behavioral context about the output structure. However, it doesn't mention potential limitations like pagination, rate limits, or error handling, leaving some gaps for a tool with no annotations.

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 front-loaded with the core purpose, followed by structured sections for usage, categories, and returns. Each sentence earns its place by providing essential information without redundancy, and the bullet-like formatting improves readability while maintaining 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 tool's low complexity (1 optional parameter), high schema coverage (100%), and the presence of an output schema (implied by 'RETURNS'), the description is complete enough. It covers purpose, usage, categories, and return format, addressing all necessary aspects without needing to explain parameters or output values in detail.

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 schema description coverage is 100%, so the baseline is 3. The description adds value by listing all categories upfront ('CATEGORIES: user, tweet, ...') and clarifying that the category parameter is an 'Optional filter', which enhances understanding beyond the schema's enum and description. This compensates well, though it doesn't provide additional syntax or format details.

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 verb 'List' and resource 'TwitterAPI.io API endpoints', specifying they are 'organized by category'. It distinguishes from siblings like 'get_twitterapi_endpoint' (singular) and 'search_twitterapi_docs' by focusing on browsing all endpoints by category rather than retrieving a single endpoint or searching documentation.

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: 'You need to browse available endpoints or find endpoints by category.' This provides clear context for usage and implicitly distinguishes it from siblings that handle authentication, specific endpoints, guides, pricing, or documentation search.

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