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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds meaningful context beyond that: sorting behavior, cursor pagination, and that it returns full tweet objects. It does not mention rate limits or auth requirements, but those burdens are partially mitigated by the strong annotation profile.

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 action and scoping, then usage rationale, return payload, and sibling alternatives. All sentences earn their place; there is no filler or irrelevant detail.

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 moderate-complexity search tool with an output schema and clear annotations, the description covers purpose, usage context, sorting, pagination, return payload, and alternative tools. An agent has enough information to call it correctly and avoid more specific sibling tools.

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% and already documents query, cursor, and queryType. The description adds value by explaining that queryType maps to sort order ('Latest (default) or Top') and that search is keyword-based across communities. This helps an agent connect the parameters to the intended behavior more naturally.

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 states a specific verb ('Search'), resource ('posts across all X Communities'), and key modifiers ('by keyword', 'sorted by Latest or Top', 'cursor-paginated'). It clearly distinguishes this tool from the sibling `get_twitter_community_tweets` by emphasizing that it covers all communities, not one specific community.

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 explicitly says when to use this tool ('find topic-specific discussion inside communities rather than on the public timeline') and names alternatives for related use cases: `get_twitter_community_tweets` to read a specific community and `get_twitter_tweet_advanced_search` for public-timeline search. This leaves no ambiguity about routing.

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