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

With no annotations provided, the description carries the burden of behavioral disclosure. It implies a read-only operation ('Search', 'Returns posts') and adds context about direct API use. But it does not disclose rate limits, auth requirements, pagination, or the difference between raw and summary modes. The core behavior is clear, but significant operational details are missing.

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 long, with the primary purpose front-loaded and a secondary sentence providing differentiation. There is no unnecessary repetition or filler; every word earns its place.

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?

For a tool with 5 parameters and no output schema, the description gives a reasonable overview: it states the input topic scope, the engagement-sorted output, and the API origin. However, it does not mention the mode parameter's return type (raw JSON vs LLM synthesis) or potential limits, leaving some gaps. The presence of a well-described schema partially compensates, so the description is adequate but not exhaustive.

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%, so the baseline is 3. The description adds little beyond what the schema already explains—'any topic' and 'sorted by engagement' give some context but do not clarify individual parameters like mode, hours, or limit. The schema itself carries the parameter documentation burden.

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 opens with a specific verb and resource: 'Search X/Twitter for social sentiment on any topic.' It clearly states the tool's function and output (posts sorted by engagement), distinguishing it from generic web search and other siblings like x_news or x_volume. The phrase 'Not available via web search' further differentiates it from site search or general query tools.

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 provides clear context: use this tool when you need X/Twitter-specific social sentiment, not general web search. It explicitly states a when-not ('Not available via web search') and notes the direct X API integration. However, it does not name alternatives like x_news or x_volume, so it lacks explicit contrast with sibling tools.

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