Search local files

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that it uses ripgrep and is fast, but does not mention potential nuances like respect for .gitignore, output format, or error behavior. Given the annotations, this is adequate but not exceptional.

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 concise and to the point, consisting of two sentences. It avoids unnecessary fluff and clearly communicates the core functionality and recommended usage.

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 description lacks essential context for effective use. With 8 parameters, no parameter descriptions, and no output schema, the agent is left without guidance on expected results (e.g., paths, line numbers), return format, or how to combine parameters. The description is too minimal to fully equip an agent to use this tool correctly in all 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?

Schema description coverage is 0%, and the description provides no explanation for any of the 8 parameters. While names like 'query', 'glob', and 'maxResults' are somewhat intuitive, the lack of any description for parameters like 'root', 'regex', or 'caseSensitive' leaves ambiguity. The tool description does not compensate for the missing schema descriptions.

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 the tool's purpose: fast local search using ripgrep, covering both file names and text contents. It distinguishes itself from file reading and listing tools by advising to search before reading large directory trees.

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 gives a clear usage context: use before reading large directory trees to avoid unnecessary scanning. It implies this tool is efficient for locating files or content, but does not explicitly contrast with sibling tools like grep or list_directory, though the context is strong enough.

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