twitter_advanced_search

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

The description discloses what the tool returns (tweet text, author info, engagement metrics, pagination cursor) and explains pagination via cursor. Annotations already declare readOnlyHint and destructiveHint, so the behavioral burden is partially met. The description adds value without contradicting annotations.

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 a single paragraph of four sentences, each serving a purpose: stating the use case, listing operators, describing output, and giving examples. No wasted words, front-loaded with the main purpose.

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 tool with 4 parameters and no output schema, the description covers the return values, pagination, and parameter usage well. It could mention authentication or rate limits, but annotations already signal read-only safety. Overall, it is reasonably 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% with parameter descriptions, but the tool description adds significant context: it explains the operators supported (from:, since:, min_faves:), provides example queries, clarifies default for count, and describes product values beyond the enum names.

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 clearly states the tool searches recent tweets using X's advanced-search operators. It specifies the verb 'search' and the resource 'recent tweets', and distinguishes itself from siblings like twitter_home_timeline and twitter_user_tweets by focusing on advanced operators.

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 provides clear context on when to use product values ('Latest' for chronological, 'Top' for engagement-ranked) and includes example queries. However, it does not explicitly exclude alternatives like twitter_user_search or state when not to use this tool.

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