List files

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

The readOnlyHint annotation already covers the safety profile, and the description adds path-scoped listing plus sorting behavior as useful context. However, it does not disclose whether the listing is recursive, whether hidden files are included, or that the tool can operate on a remote host via the host parameter.

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?

A single ten-word sentence states the verb, resource, scope, and capability with zero filler. The information is front-loaded and every word earns its place.

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?

With a 100%-covered schema, an output schema, and a readOnlyHint annotation, the structured data carries much of the burden, so the description need not explain return values or parameter formats. The remaining gaps are the lack of differentiation from list_directories and unspecified listing behavior (recursion, hidden files), which prevent the description from being fully complete for an agent deciding which tool to call.

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%, so every parameter is already documented in the input schema and the description adds no new parameter semantics. The mention of 'sorting options' merely restates the order_by and sort parameters, keeping this at the baseline of 3.

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 uses a specific verb ('List') with a clear resource ('files under a specified path') and notes sorting options, so an agent immediately understands the core operation. It does not explicitly distinguish itself from the sibling list_directories, leaving some ambiguity about whether directories are also included in results.

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 no guidance on when to use this tool versus alternatives such as list_directories or read_file. No conditions, exclusions, or prerequisites are stated, so the agent must infer the appropriate context from the tool name alone.

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