search_files

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

Discloses case-insensitivity and return format, but omits important behaviors: is search recursive? Does it skip binary files? What's the default max_results value and behavior? No annotation support.

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?

Concise and well-structured with separate sections for purpose, returns, and Args. No redundant phrases, though the Args section could be slightly more integrated.

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?

Covers purpose, return format, and parameters. Missing details on recursive behavior, default max_results value, and whether binary files or large files are handled. Adequate but not complete for full agent decision-making.

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?

Input schema has 0% description coverage. Description adds meaning for all three parameters: query (text to search), subdir (limit to subdirectory, '.' for everything), max_results (stop after N lines, 0=server default). Adds significant value beyond schema.

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?

Clearly states 'Search for a plain-text string across text files (case-insensitive)' and describes return format (matching lines with path and line number). Distinguishes from siblings like find_files (file name search).

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 explicit guidance on when to use this tool versus alternatives. Doesn't mention scope (recursive or not), file type handling, or limitations. Lacks context for optimal usage.

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