get_twitterapi_endpoint

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

Description details return values: 'Full details including path, parameters, cURL example, and code snippets.' No annotations are provided, so the description bears full burden and does so clearly.

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?

Concise and front-loaded: purpose in first sentence, usage guideline in second, and a list of examples. No unnecessary words.

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?

Tool is simple with one parameter and an output schema present. Description covers what the tool does, when to use it, and what it returns, fully meeting the needs.

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 coverage is 100%, baseline is 3. Description adds value by providing examples and usage note for the parameter, going beyond the schema's description.

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?

Description clearly states 'Get complete documentation for a specific TwitterAPI.io endpoint' with a specific verb and resource, and distinguishes from siblings by focusing on single 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?

Explicitly says 'USE THIS WHEN: You know the exact endpoint name (e.g., from search results),' providing clear context. Does not explicitly mention alternatives, but sibling tools like search_twitterapi_docs imply when not to use.

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