Search Files

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds 'FAST_DISCOVERY' but does not elaborate on behavioral traits like result limits or sorting. With annotations, baseline is acceptable but lacks added detail.

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?

Description is a single line with a tag and a sentence, extremely concise with no extraneous words. Front-loaded with '[FAST_DISCOVERY]' to immediately convey 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?

Given the presence of an output schema and simple tool purpose, the description covers the basic use case. However, it lacks parameter guidance, which is needed given zero schema description coverage. Completeness is adequate but not outstanding.

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%, meaning description adds no information about parameters beyond the schema itself. The description only mentions 'query' implicitly via examples, but does not explain project_path, all_roots, max_results, case_sensitive, or response_format.

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 it searches file paths and names, and the 'FAST_DISCOVERY' tag indicates speed. It distinguishes from siblings by advising 'use this first' for name-based searches.

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?

Explicitly says to use this first when looking for a module/feature by name, implying it's for initial discovery. Does not explicitly name alternatives but context implies differentiation from code content search.

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