X (Twitter) Search

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable context: it works without credentials (multi-engine + oEmbed fallback) and mentions the official API path. This goes beyond what annotations provide, though it could detail fallback behavior more.

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 two sentences, front-loaded with the main capability. It is concise without wasted words, but could be slightly more structured (e.g., separating search types from credential notes).

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?

Despite having an output schema, the description does not explain how different search types require specific parameters (e.g., thread needs post_id, user needs username). It lacks completeness for a tool with 7 parameters and multiple search modes.

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 only 29% (only to_date and from_date have descriptions). The description does not explain any parameters, such as how query, post_id, username, or max_results relate to the search types. Given low coverage, the description should compensate but does not.

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 performs real-time X/Twitter search with four specific types: keyword, semantic, user profile, or thread. It also mentions credential modes. However, it does not explicitly differentiate from sibling tools like fused_search or search_layer, which could be helpful for selection.

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 that the tool works without credentials but has an official path via grok login or XAI_API_KEY. This provides some context on authentication, but it does not give any guidance on when to use this tool versus sibling tools or what prerequisites are needed for each search type.

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