Search X (Twitter) live

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

No annotations provided, so description must carry behavioral disclosure. It mentions account requirement (logged-in Grok) and mode behavior (deep adds timeline, quotes, etc.). However, it does not cover rate limits, data retention, or potential side effects. Adequate but not rich.

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?

Two sentences efficiently convey purpose and key behavior without fluff. Front-loaded with the main action and essential context.

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?

No output schema exists, and the description gives a high-level outline of returns (summary, source items, citations) but lacks detail on structure. Parameter details are covered by schema. Adequate for a search tool but leaves some gaps in return 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the mode parameter's additional features (timeline, quotes, perspectives, sentiment, verification) beyond the schema enum descriptions. For other parameters, schema descriptions are sufficient.

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 searches live X/Twitter posts using a Grok account and lists return components (summary, source items, citations). It implicitly differentiates from siblings 'bluex_health_check' and 'bluex_web_search' by focusing on X/Twitter, but does not explicitly contrast them.

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 on when to use this tool versus alternatives, and no explicit when-not scenarios. The description only mentions basic vs deep mode effects but provides no decision criteria for choosing between them.

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