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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses pagination behavior ('Returns ~20 tweets per page'), ordering ('reverse chronological order' vs 'Top'), and date semantics ('until:' is exclusive). It even warns that older/archival queries should use date ranges rather than pagination, which is useful behavioral guidance.

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 a bold primary-purpose statement, followed by compact examples and a short general section. Every sentence contributes either selection guidance, query syntax, or behavioral details, with no filler.

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?

The description covers when to use, query syntax, date format, ordering, and pagination. It would be slightly stronger if it described the shape of a returned tweet object, since there is no output schema, but the current information is sufficient for correct tool selection and invocation.

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 for parameters is 100%, so the baseline is 3. The description adds real value through example query constructions like 'from:USER since:X until:Y', the default for queryType ('Default to Latest for time-sensitive queries'), and the YYYY-MM-DD format rule, going beyond the schema text.

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 by naming it the 'PRIMARY CHOICE for date-range / historical / keyword-based tweet queries' and then states 'Search Twitter/X for tweets matching a query.' It clearly distinguishes itself from get_user_last_tweets and other siblings, so an agent can identify it without reading schemas.

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?

It gives explicit when-to-use instructions with examples ('tweets from January 2026', 'tweets last week'), and an explicit exclusion ('Use this (NOT get_user_last_tweets) whenever user asks about a SPECIFIC TIME RANGE or historical tweets'). It also lists general use cases like keyword research and brand monitoring.

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