kimi_grep

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

With no annotations, the description carries the full behavioral disclosure burden but only says 'Search for regex patterns in files.' It does not mention recursive behavior, output format, default path handling, or relationship between glob and path, leaving critical behavioral aspects undisclosed.

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 one short sentence with zero filler words, front-loaded with the key action and target. It achieves maximum conciseness, though the brevity comes at the cost of behavioral detail captured in other dimensions.

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?

Without an output schema or annotations, the description should explain search scope, result format, and parameter interactions, but none are covered. The one-line description provides only the core purpose, making it insufficient for reliable invocation in complex scenarios.

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 input schema already describes pattern, glob, and path, covering 75% of parameters, so a baseline of 3 is appropriate. The description adds no additional parameter semantics and leaves workFolder entirely undocumented in both schema and description.

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 uses the specific verb 'Search' and identifies the resource as 'regex patterns in files,' making clear this is a content-grep tool. It does not explicitly differentiate from sibling tools like kimi_glob, but the regex-in-files phrasing conveys the core purpose adequately.

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?

There is no guidance on when to use this tool versus alternatives such as kimi_glob for filenames or kimi_shell for system operations. The description only states the basic function and lacks any usage context, exclusions, or recommended scenarios.

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