search_user_chats_api_v1_chats_search_get

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

No annotations are provided, and the description fails to disclose any behavioral traits such as pagination, authentication requirements, rate limits, or whether the search is read-only. The schema suggests pagination via the 'page' parameter, but the description does not mention it.

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 overly brief (3 words) and lacks essential details. While short, it does not earn its place as it provides insufficient information for an agent to use the tool correctly.

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?

Given the complexity of a search tool with pagination, the description is completely inadequate. It does not explain the search scope, return format, or behavior, relying entirely on the output schema (which is not provided in the description).

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?

With 0% schema description coverage, the description adds no meaning to the parameters. 'text' is required but not explained (e.g., what it searches against), and 'page' is optional with no explanation of its purpose.

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 'Search User Chats' is vague and does not differentiate from sibling tools like 'get_session_user_chat_list_api_v1_chats' or 'get_user_chat_list_by_tag_name_api_v1_chats_tags_post'. It lacks specificity on what is being searched (e.g., by text, tags, or content).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, scope (e.g., current user only), or context for using the search functionality.

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