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

Annotations already declare this as a read-only, open-world, idempotent, non-destructive operation. Beyond that, the description adds useful behavioral context: X search operator support, category-specific behavior for Latest and People, and pagination. It does not discuss rate limits or authentication, but the annotation coverage lowers the burden.

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 front-loaded with the core purpose and then efficiently covers operators, category behavior, and pagination. The operator list is dense but purposeful; no sentence is wasted, though it could be slightly more compact.

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 search tool with full schema coverage and strong annotations, the description covers the key behavioral details an agent needs: query operators, category tabs, and pagination. Return formatting and truncation behavior are handled by the schema, so the description is largely complete.

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 all parameters are already documented in the schema. The description still adds value by explaining supported X search operators for searchItem and clarifying category semantics for Latest and People, going beyond the enum labels 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?

States a specific verb and resource: 'Search X like the search box'. It also clarifies category behavior, including that People returns accounts rather than tweets. It does not explicitly distinguish itself from siblings like get_user_tweets or search_communities, so it falls short of full sibling differentiation.

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 gives implied usage through operator examples and category behavior, which helps an agent understand how to use search effectively. However, it does not explicitly say when to choose this tool over alternatives such as get_user_tweets, get_tweet, or search_communities.

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