list_files

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

No annotations exist, so the description must disclose behavioral traits. It mentions 'smart ignore patterns' but does not explain what that means (e.g., .gitignore-like rules? any special behavior?). No details about performance, side effects, or access requirements.

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?

Two concise sentences that get to the point. However, 'smart ignore patterns' is somewhat vague and could be more precise. Overall, tightly written with no wasted 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 tool with 4 parameters and no output schema or annotations, the description is somewhat complete but lacks details on return format, pattern syntax, and behavior when patterns are combined. It's sufficient for basic understanding but not fully self-contained.

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% and the input schema provides descriptive parameter names and defaults. The tool description adds only the phrase 'smart ignore patterns' which adds minimal value beyond the schema's own descriptions.

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 lists files in a directory, with a specific verb ('List') and resource ('files in a directory'). It adds 'smart ignore patterns' to distinguish from simpler list tools. Sibling tools include 'find_files' and others, so this description sets it apart.

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 usage for directory exploration with pattern filtering, but provides no explicit guidance on when to use this vs. sibling tools like 'find_files' or when not to use. No alternatives or exclusions mentioned.

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