twitter-intel

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

No annotations are provided, so the description carries the full burden. It describes the actions and output for each, but does not disclose rate limits, authentication needs (beyond 'without an API key'), error handling, or data freshness. The mention of 'x402-settled upstream' is cryptic. Adds some value but lacks full transparency.

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?

Three sentences with no wasted language. The most important information (real-time data without API key) is front-loaded. Each sentence covers a distinct aspect: general value, lookup_user, search_tweets, and a technical note.

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 no output schema and no annotations, the description is adequate for a simple tool but lacks details on pagination, rate limits, output format, or error handling. It covers the basics but could be more complete for robust agent usage.

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%, baseline 3. The description adds meaningful context by explaining the return for each action (full profile vs. 10 tweets) and reinforcing the required parameters for each action. This goes beyond the schema alone.

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 it provides real-time Twitter/X data without an API key and specifies two distinct actions: lookup_user (returns full profile) and search_tweets (returns 10 recent tweets). This distinguishes it from sibling tools like social-intel or reddit-intel.

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 mentions it works without an API key, which is a key context for use. It implies when to use it (for Twitter data) but does not explicitly state alternatives or exclusions. Still clear enough for an agent.

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