list_files

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

The description discloses that it does not follow symbolic links, which is a key behavioral detail. However, without annotations, it does not mention other important behaviors such as permission handling or how recursion works.

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?

The description is a single, concise sentence that is front-loaded with the primary action. Every word is necessary, and there is no superfluous content.

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 tool has 4 parameters and no annotations, the description is insufficient. It lacks context about the path relative to the workspace, recursion behavior, and session ID requirements. The presence of an output schema partially compensates, but overall completeness is low.

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 coverage, the description adds no information about the four parameters (path, max_depth, recursive, session_id). The schema provides defaults and titles, but the description fails to explain their meaning or context.

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 it lists regular files and directories without following links, distinguishing it from siblings like read_file or delete_files. However, the phrase 'beneath /workspace' is somewhat ambiguous regarding the path parameter's relationship to the workspace.

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 is provided on when to use this tool versus alternatives like read_file or write_files. The description does not mention prerequisites or typical usage scenarios.

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