list_files

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

No annotations are provided, so the description carries the transparency burden. It states the core behavior (list files/subdirectories) but does not disclose details such as path validation, hidden-file behavior, sorting, or error handling. For a read-only listing tool this is minimally acceptable but not rich.

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, front-loaded sentence that conveys the full purpose without redundancy or filler. It is appropriately minimal for the tool's simplicity.

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?

For a simple listing tool with one optional parameter and an output schema, the description is largely complete. It defines scope (files/subdirectories in a directory) and context (Nutstore), but could add a note about immediate vs recursive listing or path handling to fully cover edge cases.

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 schema has one 'path' parameter with 0% description coverage. The description's '指定目录' clarifies that the path parameter refers to a directory, adding some meaning beyond the schema's type/default. However, it does not explain path format, accepted values, or interaction with the default '/'.

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 the action ('列出' / list) and the resource ('指定目录下的文件和子目录' / files and subdirectories in a specified directory) for Nutstore. It effectively distinguishes listing from sibling tools like search_files (searching) or get_directory_tree (tree view).

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 implies the tool is for listing immediate files and subdirectories under a path, but it does not explicitly mention when to prefer it over alternatives like get_directory_tree or search_files. No exclusions or sibling references are provided.

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