ai_search_doubao

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

The description discloses that the tool automatically waits for completion, may return a taskId on timeout, and allows later retrieval via a separate result tool. This is useful behavioral context beyond what annotations (which are absent) would provide.

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 extremely concise (2 sentences) and front-loaded with the core purpose. Every sentence adds value and there is no redundant or filler text.

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 presence of an output schema (not shown, but indicated), the description does not need to explain return values. It covers purpose, parameter roles, timeout behavior, and a retry mechanism, making it reasonably complete for this tool.

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 compensates by explaining 'inquiry_text' (search query) and implying 'timeout_seconds' usage. It adds meaning beyond the bare schema, though it does not detail the range or format of the timeout.

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 it performs an AI-powered search using '豆包联网' (Doubao) and returns results. It distinguishes itself from siblings like 'ai_search_kimi' and 'ai_search_deepseek' by branding, but does not differentiate its scope or behavior.

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 for search queries and mentions timeout handling with a fallback to 'ai_search_doubao_result'. However, it does not explicitly state when to use this tool versus other search tools, nor does it specify prerequisites or limitations.

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