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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new operational context: roughly 20 results per page and the need to use cursor to paginate, which an agent needs to avoid treating one page as a complete result set.

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 sentences, front-loaded with purpose, then pagination mechanics, then the disambiguation pointer. No filler and nothing buried.

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 three-parameter read-only search with no output schema, the definition covers purpose, scope, page size and pagination well enough to call correctly. The only soft gap is that the shape of a returned tweet is not hinted at, which is acceptable given the annotations and low complexity.

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 query, cursor and queryType are already documented, including the enum meanings and the "omit or empty string for first page" rule. The description adds only the page-size context and the keyword-only constraint, so baseline 3 applies.

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 tweets") plus a precise scope ("across all X Communities by keyword"), which is exactly what separates it from a global tweet search. An agent can distinguish it from search_tweets without inspecting either schema.

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?

Explicitly routes the agent to search_tweets for global search, which is the most likely confusion point. It does not address when to prefer this over community-scoped siblings like get_community_tweets, though "across all X Communities" implicitly signals the multi-community breadth.

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