socials_x_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds meaningful context such as the default mode ('top (default)'), time formats (YYYY-MM-DD vs Unix), and query syntax (#hashtags, @mentions, -exclusions). However, it omits details like return format, pagination, and authentication, so it falls short of full transparency.

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, well-structured paragraph with an opening summary sentence followed by a categorical breakdown. Every sentence provides useful information, and there is no redundant content. It is appropriately sized for the 22-parameter 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?

For a complex search tool with 22 parameters and no output schema, the description thoroughly covers input semantics, including modes, filters, and time handling. However, it lacks any mention of return format, pagination, or limitations, which would be needed for full completeness. The absence of output schema documentation is a notable gap.

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 schema already has 100% coverage, but the description adds significant value by grouping parameters into logical categories (User, Time, Engagement, Content, Location, Modes) and explaining how operators combine, e.g., 'since/until (YYYY-MM-DD) or since_time/until_time (Unix)'. It also elaborates query syntax beyond the schema's property descriptions.

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 'Advanced X search with full operator support,' identifying the tool as a comprehensive search tool for X. It distinguishes itself from sibling tools like socials_x_profile or socials_x_notifications by focusing on search capabilities and operator syntax, making its purpose unambiguous.

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 by detailing operator categories and query syntax, but it does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or comparisons with sibling search-related tools are provided, leaving usage guidance implicit.

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