search_tweets

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

Without annotations, the description carries the full transparency burden but only notes that results are 'recent' and lists filters. It does not disclose pagination, result limits, rate limits, or return format, leaving significant behavioral ambiguity.

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, front-loaded sentence that mentions the core action (search), resource (recent X posts), and optional filters without wasted words.

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 tool has no annotations or output schema, so the description should explain return values and usage context more fully. It omits result details, pagination, and any guidance relative to sibling search tools, leaving the agent under-informed.

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 60%, with since/until/from_user already described. The description adds general meaning by mapping keyword, language, dates, and author filter to the parameters, but does not provide deeper detail on format or constraints beyond that.

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?

Description clearly states a search over recent posts with keyword and optional filters, giving a specific verb and resource. It does not explicitly distinguish itself from sibling tools like x_search, though 'recent' and the filter list help narrow its scope.

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 implies usage: use this tool to search recent posts by keyword with optional language, date, and author filters. It does not explicitly state when to prefer this over x_search or x_search_status, nor does it mention any exclusions.

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