list_files

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

The description discloses RBAC enforcement (access control) and the return format (relative paths from repo root). No annotations are provided, so the description carries the full burden, and it adds meaningful behavioral context beyond the schema.

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, zero wasted words. The first sentence captures the core action and access model, the second explains the output. Information is front-loaded and easy to parse.

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 the low complexity (1 required parameter with enum, output schema exists) and sibling tools, the description covers the essential behavior: what it lists, where, and what returns. Minor gaps like recursion depth or sorting are not critical for this 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?

With 0% schema description coverage, the description must compensate. It explains that the 'domain' parameter corresponds to a subdirectory under 'data/', which adds meaning beyond the enum list in the schema. This helps the agent understand the parameter's role.

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 'List files under data/<domain>' which is a specific verb and resource. It distinguishes from sibling tools like read_file (reads a single file) and search (queries content) by focusing on listing files within a domain directory.

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 explicit guidance on when to use this tool versus alternatives. It does not state prerequisites, when not to use, or mention any filtering capabilities. The description implies usage for listing files in a domain but lacks context for decision-making.

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