list_filesGet a complete inventory of files in the store, showing size, SHA256 hash, public URL, and last update time for each file.
Every file in the store with its size, sha256, public URL and last update.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the output fields and implies a read-only bulk operation, but it does not mention pagination, potential large payloads, or any authentication requirements. For a listing tool this is a moderate gap, but the core behavior is clear.
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 states the scope ('Every file') and the relevant fields. No fluff or unnecessary detail.
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 parameterless listing tool without an output schema, the description adequately conveys the return content and scope. It does not mention ordering or limits, but these are minor for a simple inventory operation. The tool is sufficiently complete for an agent to call it correctly.
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?
There are zero parameters, so the description does not need to explain them. The baseline for 0 params is 4, and the description correctly adds no redundant parameter information.
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 verb 'list' and resource 'files', and specifies the exact fields returned (size, sha256, public URL, last update). This distinguishes it from siblings like get_file (single file) and put_file (upload) without ambiguity.
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 this is the tool for obtaining a complete inventory of files, but it does not explicitly mention when to use it over get_file for a single file or delete_file for removal. The context is clear, but no explicit alternatives or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.