x_open_search

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

No annotations are provided, so the description carries the full burden. 'Open' implies a UI-navigation or state-changing action, but the description never says whether it mutates app state, requires an active session, or what happens to the current view. Behavioral disclosure is largely absent.

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 tight sentence that front-loads the action and states options briefly. No waste, though its brevity borders on under-specification for a tool with many similar siblings.

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 simple two-parameter tool, the description is minimally sufficient, but with no annotations and ambiguous framing versus the search siblings, it leaves the agent unsure of the tool's exact effect and place in the workflow.

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 both parameters are already documented. The description's 'prefilled with a query and live filter' loosely maps to the query and mode parameters but adds no format, enum values, or constraint detail beyond the schema, matching the baseline of 3.

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 (Open) and resource (X search), giving a clear high-level action. However, it does not differentiate from siblings like x_search_posts, x_search_profiles, or x_search_communities that actually execute searches, so an agent cannot easily tell whether this navigates a UI or runs a query.

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 guidance on when to use this versus the many sibling search tools. The word 'optionally' implies it can be called with no arguments, but the description never states the conditions or alternatives that select this tool.

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