Glob

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the basic return behavior but omits important details such as whether paths are absolute or relative, whether matching is recursive, how hidden files are handled, and what happens when no files match.

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 short, front-loaded, and easy to parse. The second sentence adds context but is somewhat redundant with the first, keeping it from a perfect score.

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 one-parameter tool without an output schema or annotations, the description is only minimally adequate. It gives the core behavior but leaves out pattern-language details and behavioral edge cases needed 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?

The pattern parameter has zero schema description coverage, and the tool description does not compensate by explaining expected glob syntax, examples, or supported wildcards. The agent is left to infer pattern semantics entirely from the parameter name and the tool name.

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 function returns a list of files matching a given pattern, which is a specific verb and resource. It does not explicitly differentiate itself from sibling tools, but the core purpose is unmistakable.

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 says the function is 'useful for finding files in a directory,' which gives some context for when to use it. However, it does not mention alternatives, exclusions, or when a sibling like grep or read_file would be preferable.

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