xhs_search

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

Annotations already declare the tool safe (readOnlyHint, idempotentHint, non-destructive). The description adds useful context about the dependency on an existing signed web request and the current Chrome session, which informs the agent about authentication and browser state requirements. This goes beyond the annotations without contradiction.

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, concise sentence that immediately states the action and key context. There is no filler or redundancy; it efficiently conveys both what the tool does and a critical operational requirement.

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 with three parameters, an output schema, and safety annotations, the description covers the core purpose and the main contextual dependency (the Chrome session). It does not mention result limits or failure modes, but the output schema likely handles return values, so the description is sufficiently complete for the tool's complexity.

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 description provides no explanation of the parameters (keyword, page, sort), and schema description coverage is 0%. While the parameter names are somewhat self-explanatory, the description does not compensate for the lack of schema descriptions, leaving the sort enum semantics and page behavior to inference. The verb 'Search' only implicitly hints at a keyword.

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's purpose: 'Search Xiaohongshu' via a 'signed web request in the current Chrome session.' The verb 'Search' and resource 'Xiaohongshu' are specific, and the mention of the signed web request distinguishes it from generic search tools and indicates an authenticated context.

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 that this tool should be used when searching Xiaohongshu requires an authenticated browser session, as it explicitly references 'the current Chrome session.' However, it does not explicitly mention when not to use it or compare with sibling tools like xhs_note or xhs_user_notes, so it lacks full exclusion guidance.

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