glob

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

Description adds detailed behavioral context beyond annotations: supported patterns, return format, and that it only matches files. The store parameter explanation about persistence is also provided.

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?

Three sentences, each concise and informative: purpose, pattern support, return type and constraint. No unnecessary words.

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 glob matching tool with two simple parameters and no output schema, the description fully covers purpose, behavior, and constraints. Sibling tools are diverse, and the description is sufficient for correct 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 descriptions are present for both parameters. Description adds value with pattern examples and cross-session storage behavior, exceeding what the schema alone provides.

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?

Clearly states 'Find files matching a glob pattern' with examples of wildcards, recursive matching, and brace expansion. Distinguishes from siblings by specifying it returns files only and not directories.

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?

Does not explicitly state when to use this tool versus alternatives like ls or grep. The description implies its domain but lacks direct guidance on context or exclusions.

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