search_tweets

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'Search X for posts matching a query', implying a read-only operation but omitting details about rate limits, authentication needs, or result structure. No explicit confirmation that it is non-destructive.

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?

A single 6-word sentence that is front-loaded with the action and resource. No wasted words; every part contributes to understanding. Ideal conciseness for a simple tool.

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?

Given the presence of an output schema and three clear parameters, the description is minimally adequate. However, it lacks context about what 'posts' refers to (e.g., tweet objects), potential pagination, or search behavior nuances. An agent would need to infer specifics from the schema and tool name.

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 baseline is 3. The description itself does not add any parameter-specific meaning beyond what the schema already provides (e.g., limit, latest, query). The description's generic 'matching a query' is covered by the schema.

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 verb 'search', the resource 'X for posts', and the mechanism 'matching a query'. It is specific but does not explicitly differentiate from sibling tools like get_tweet or get_user_tweets, though the verb 'search' implies broad querying.

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 no guidance on when to use this tool versus alternatives (e.g., get_tweet for specific tweets, get_user_tweets for timeline posts). No context about prerequisites or when not to use it is provided.

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