x_search

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a useful behavioral trait: it operates 'through the user's current Chrome session', implying dependency on browser state/login. No contradictions with annotations.

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 sentence of 14 words, front-loaded with the core purpose. Every word adds value—it names the resource, the action, and the key contextual detail (Chrome session). No unnecessary elaboration.

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 search tool, the description covers the essential purpose and a key context (Chrome session). However, it lacks usage guidance relative to other search tools, and parameter semantics are undocumented. Output schema and annotations provide additional structure, but the description alone is not fully complete for an agent to use it confidently.

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% (no descriptions for keyword, sort, or limit in the main properties). The tool description does not explain these parameters at all, failing to compensate for the schema gap. The sort enum has a brief description in the schema, but keyword and limit remain unexplained.

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 a specific verb and resource: 'Search X (formerly Twitter) posts'. It also adds context about using the user's Chrome session. However, it does not explicitly differentiate from sibling search tools like google_search or zhihu_search, though the platform-specific resource makes the purpose fairly 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 when to use this tool: when you need to search X posts, particularly via the user's existing Chrome session. It does not mention alternatives, exclusions, or prerequisites (e.g., being logged in), so guidance is minimal but not absent.

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