glob

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

With no annotations provided, the description carries the full behavioral burden. It adds useful details such as using pathlib's glob matching and supporting recursive patterns, hidden-file filtering, and result limiting. It does not disclose edge-case behaviors like symlink handling or error conditions, so it is adequate but not fully transparent.

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 two compact sentences with no filler. The core purpose is front-loaded, and the implementation detail and feature highlights are presented efficiently.

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 fully documented input schema and the presence of an output schema, the description is largely complete for a glob-finding tool. It adds the key implementation note about pathlib glob semantics, though a small amount of additional usage guidance relative to sibling tools would make it fully complete.

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 input schema has 100% description coverage for parameters, so the schema already documents path, pattern, recursive, max_results, and include_hidden. The description only lightly reinforces these concepts, which meets the baseline but adds no significant new parameter semantics.

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 that the tool finds files matching a glob pattern, using a specific verb and resource. It distinguishes itself from file content tools and directory listing tools, though it does not explicitly contrast with the sibling search_files tool.

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 implies when to use the tool: when a glob pattern is needed to locate files. However, it does not explicitly state when to prefer an alternative such as search_files or list_dir, leaving some routing decisions to inference.

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