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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-web profile is covered. The description adds two genuinely useful behavioral facts the annotations do not: that native X search operators are honored in the query, and that each call costs 1 credit. It stops short of describing result volume or pagination behavior.

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 short fragments, front-loaded with the core purpose, and the credit cost is appended rather than buried. It is efficient to the edge of being terse, but no sentence is wasted.

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, so the description should carry more of the load regarding return shape and result counts, and it does not. Most critically, it offers no way to distinguish this tool from the near-identical twitter_search_posts sibling, leaving a real routing ambiguity unresolved.

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% with self-documenting parameters (query, type enum, cursor), so the baseline is 3. The description adds modest surplus meaning by telling the agent that X search operator syntax is valid in the query string, which the schema does not state.

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?

States a specific verb and resource ('Search X posts'), which is unambiguous on its own. However, it does nothing to distinguish itself from the sibling twitter_search_posts, which by name appears to do nearly the same thing, so an agent cannot route confidently between them from the description alone.

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?

'X search operators work' hints at query syntax capability but is not when-to-use guidance. There is no statement of when this tool is preferable to twitter_search_posts, twitter_trends, or twitter_user_tweets, and no mention of pagination expectations despite a cursor parameter.

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