list_directory

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

The description explains the return format and automatic exclusion of blocked paths, but does not explicitly state that the operation is read-only or disclose any side effects. With no annotations, more behavioral context would be helpful.

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 sentences efficiently convey the return structure, listing behavior, and special cases. No extraneous information.

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 no output schema, the description fully describes the return object and mentions blocked path exclusions. The tool is simple with one optional parameter, and the description covers all necessary context.

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 parameter 'path' is described with usage instructions (omit or empty for root), adding meaning beyond the schema's type and default. This exceeds the baseline expectation even with high schema coverage.

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 returns a structure { root, path, entries[] } with entries having name, type, and relative path. It distinguishes itself from sibling tools like list_schemas by focusing on directory contents.

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 provides explicit guidance on how to list the root by omitting path or passing '', and mentions blocked paths are automatically excluded. However, it does not compare to alternatives or provide when/when-not advice.

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