tweetapi_endpoint_lookupFind likely TweetAPI endpoint docs by path or keyword to locate the API reference for a given TweetAPI task.
Find likely TweetAPI endpoint docs by path or keyword.
| Name | Required | Description | Default |
|---|---|---|---|
| pathOrKeyword | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds that lookup works by path or keyword and uses 'likely' suggesting fuzzy matching, but it does not disclose output format, pagination, or any other behavioral traits.
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 a single sentence that is front-loaded and free of filler. Every word contributes to understanding the tool's purpose and input.
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?
The tool is simple with one parameter and strong annotations, but the lack of an output schema means the description should clarify what the lookup returns (e.g., links, content, or a list). The phrase 'Find likely... docs' leaves ambiguity about the result format.
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?
With 0% schema description coverage, the description compensates by clarifying that the sole parameter 'pathOrKeyword' accepts either a path or a keyword. This adds meaningful semantics beyond the bare schema, though it lacks concrete examples.
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 a specific action ('Find'), a clear resource ('TweetAPI endpoint docs'), and the search approach ('by path or keyword'). It distinguishes itself from sibling tools like tweetapi_docs_search by focusing on locating endpoint docs rather than general documentation pages.
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?
No guidance is provided about when to use this tool versus alternatives. The description implies its use for finding docs, but does not mention when to prefer tweetapi_docs_search or tweetapi_docs_get_page, nor does it state exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.