kimi_web_search

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

With no annotations, the description has the full burden of disclosing behavioral traits. It mentions 'AI-summarized' outputs but does not state whether the operation is read-only, any rate limits, prerequisites, or side effects. The safety profile of the tool is entirely unspecified.

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 efficient sentence with no redundancy. It is front-loaded and easy to scan. However, it may be too terse given the missing parameter explanations and behavioral context.

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?

The tool has three parameters, no output schema, and no annotations. The description does not explain the return format (beyond 'AI-summarized'), the purpose of 'workFolder', or any usage constraints. Key contextual information is missing for a complete understanding.

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 schema describes 'query' and 'max_results', but the description adds no extra meaning for these parameters. The 'workFolder' parameter lacks any schema description and is not explained in the tool description. With only 67% schema coverage, the description should compensate but does not.

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 action ('Search the web') and a unique property ('AI-summarized results'), distinguishing it from sibling tools like kimi_fetch_url which fetches a specific URL. The purpose is immediately understandable.

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. It does not mention conditions, exclusions, or differences from related tools such as kimi_fetch_url or kimi_research. The user is left to infer when a web search is appropriate.

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