Locate files in a shared project by matching glob patterns, enabling quick retrieval of specific files.
Search for files matching a glob pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | Yes | Glob pattern | |
| max_results | No | Maximum results (default: 50) |
Changes observed during successful MCP inspections.
v1.11.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden of behavioral disclosure. It only says 'Search for files matching a glob pattern' and does not mention whether the search is recursive, how hidden files are handled, what the return format is, or whether max_results has implications. This is a significant gap for a tool with zero annotation coverage.
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 a single, front-loaded sentence with no wasted words. It efficiently communicates the core action and resource.
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?
For a simple tool with no output schema and no annotations, the description is incomplete. An agent would lack information about default behaviors, return structure, or edge cases. It is minimal to the point of being under-specified for reliable invocation.
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 100%, so both parameters are already documented in the schema. The description adds minimal value beyond repeating the pattern concept; it does not clarify glob syntax or provide examples. Baseline of 3 is appropriate given high schema coverage.
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 states a specific verb (search) and resource (files) with a clear method (glob pattern). It is distinct from siblings like list_files (which lists files in a directory) and grep_content (which searches file contents), though it does not explicitly name alternatives.
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 guidance is provided on when to use this tool versus siblings such as list_files or grep_content. The description only states the basic function without any context on selection criteria, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.