x_search_posts

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds one genuine behavioral fact — results are limited to 'recent' posts, not the full archive — but says nothing about rate limits, authentication requirements, result volume, or how results are ordered, leaving meaningful behavioral gaps for a search tool.

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 front-loaded sentence with no wasted words. It is efficiently sized, though the extreme brevity is part of why other dimensions are thin.

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?

With no output schema, 0% parameter description coverage, and only a readOnlyHint annotation, the description would need to carry most of the load. Instead it omits the query syntax details, the meaning of maxResults, and any sense of the returned result shape, so an agent cannot call this confidently without outside knowledge.

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 0%, so both parameters are undocumented in the schema. The description nods at 'official X query syntax' for the query parameter but gives no operators, examples, or format rules, and it says nothing at all about maxResults (its default of 10, its 10-100 range, or how it interacts with the query).

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?

States a specific verb ('Search') and resource ('recent X posts'), which is clear on its face. It does not, however, distinguish itself from siblings such as x_get_user_posts or x_get_post, which also return posts, so the agent must infer the distinction from the verb alone.

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?

There is no explicit when-to-use guidance, no conditions or exclusions, and no reference to the sibling tools that also retrieve posts. The word 'recent' implies a temporal scope but the description never tells the agent when search is preferable to x_get_user_posts or x_get_post.

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