Search Posts

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

Annotations already declare this as read-only, idempotent, and non-destructive, so the description does not need to repeat safety traits. It adds meaningful behavioral context by revealing the 7-day time window and the supported query syntax (keywords, hashtags, operators), which goes beyond the generic search intent.

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 two sentences long and front-loaded with the core purpose. Every word earns its place, with no redundant or filler content.

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 a modest complexity (3 params, no nested objects) and the annotations cover safety. The description adequately conveys the search scope and time window. While it doesn't describe return values, the response_format parameter hints at output shapes, and the tool is simple enough that a full return specification is not critical.

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?

The input schema already provides 100% coverage with descriptions for all three parameters. The description adds no new parameter-specific meaning beyond what the schema states; it merely echoes the query capabilities already listed in the schema's query parameter description.

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 for recent posts (last 7 days) matching a query, using a specific verb ('search') and resource ('posts'). It distinguishes itself from sibling tools like x_get_user_posts or x_get_my_timeline by being a general search across posts rather than a user-specific or timeline-based retrieval.

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 context by noting the 7-day recency window and support for keywords, hashtags, and X search operators. It doesn't explicitly name alternatives or exclusions, but since there is no other general search tool among siblings, the intended use is clear.

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