Search Files

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

The description discloses recursive behavior, return of full paths, and constraint to allowed directories. Annotations already indicate readOnlyHint=true, and the description adds behavioral context beyond that without contradiction.

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 five sentences, front-loaded with purpose, then pattern details, use case, and constraint. Every sentence adds value with no redundancy or fluff.

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?

With an output schema present, the description does not need to explain return values. It covers recursive search, pattern syntax, and access constraints, providing complete context for a search 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?

The description explains the pattern parameter with glob-style pattern examples and relative path convention. The path parameter is implied as relative to working directory. However, excludePatterns is not described. Given 0% schema coverage, the description compensates significantly but not fully.

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 'Recursively search for files and directories matching a pattern', providing a specific verb and resource. It distinguishes from sibling tools like list_directory or file reading by focusing on pattern-based recursive 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?

The description mentions 'Great for finding files when you don't know their exact location', giving usage context. It does not explicitly state when not to use or list alternatives, but the purpose is clear enough for an agent to decide.

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