glob

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

With no annotations, the description carries the full burden. It states the tool is 'Fast' and 'Returns matching file paths,' implying a read-only search. But it doesn't disclose edge-case behaviors like hidden file handling, case sensitivity, or behavior on unmatched patterns. For a simple read-only tool, this is adequate but not rich.

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 four short sentences, each serving a purpose: purpose, examples, return value, and usage. It is front-loaded with the core function and contains no fluff or redundancy.

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 two-parameter tool with no output schema, the description adequately covers purpose, usage, and return value. It lacks edge-case details (e.g., empty results) but is sufficiently complete for an agent to select and invoke the tool correctly. Sibling context makes the distinction from grep clear.

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%, providing baseline 3. The description adds value with pattern examples ('**/*.js', 'src/**/*.ts'), illustrating the accepted syntax beyond the schema's generic 'glob pattern' description. This pushes it to a 4.

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 performs 'file pattern matching' and explicitly says it 'Returns matching file paths.' It distinguishes from siblings like grep (content search) and read (file reading) by focusing on finding files by name pattern, with concrete examples (**/*.js, src/**/*.ts).

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?

It gives explicit usage guidance: 'Use it to find files by name pattern.' Avoids ambiguity about its purpose. However, it does not mention alternatives or exclusions (e.g., when to prefer grep for content search), which would make it a 5.

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