list_directory

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

No annotations provided; description says 'with metadata' but does not specify what metadata or note any behavioral traits (e.g., read-only nature, permissions).

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?

Single sentence, concise, but omits important details like return format and scope. Front-loaded with purpose, but incomplete.

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?

No output schema; description fails to specify what metadata is returned (size, date, type, permissions). Also lacks detail on whether listing is recursive. Incomplete for a file listing tool.

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 covers both parameters with descriptions; description adds no extra meaning beyond 'with metadata', which is about output, not parameters. Baseline 3 for 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?

Description clearly states it lists files and directories with metadata, distinguishing it from get_file_info (single file) and search_files (search). Could be more specific about scope (e.g., current directory vs. recursive).

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?

No guidance on when to use this tool versus siblings like get_file_info or search_files. Agent must infer from name and description.

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