search_files

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

Reveals key behaviors: recursive search, case-insensitive matching, allowed directories restricted to /app. No annotations are provided, so description carries the burden and does well.

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?

Three concise sentences, front-loaded with main purpose, no fluff. Every sentence adds value.

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?

Adequately covers search behavior and constraints, but lacks mention of output format (e.g., list of paths) which is reasonable given the context.

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?

Schema coverage is 100%, but description adds meaning beyond schema by specifying pattern as 'substring match', path default, and exclude patterns as glob relative to search path. Also adds case-insensitivity not in 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?

Description clearly states a specific verb ('Recursively search') and resource ('files/directories'), and distinguishes from siblings like list_directory or directory_tree by emphasizing recursion and case-insensitive matching.

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?

Provides usage hints for exclude_patterns and restricts scope to /app, but no explicit when to use vs. alternatives or when not to use.

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