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

No annotations are provided, so the description carries the full burden, and it discloses nothing: no result format, ordering, pagination/limit behavior, recursive vs flat semantics, or permissions. A read tool for a storage namespace has many behaviors an agent needs to predict results, and none are present.

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 sentence is terse with no filler, but it is under-specified rather than concise: three words convey no information beyond the tool name. There is no structure to front-load because there is no 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?

With no output schema, no annotations, and an undocumented parameter, the description leaves an agent unable to call the tool correctly or predict what comes back. At minimum it should explain prefix semantics and whether results are recursive across the storage namespace.

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 0% and the description never mentions the sole "prefix" parameter. Whether prefix is a path prefix, a name filter, or a delimited pseudo-directory selector is entirely left to guesswork, so the description fails to compensate for the schema gap.

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?

"List stored files" names a specific verb and resource, which is enough to know it enumerates files. However, it does nothing to separate itself from the many sibling list/read tools (storage_list, storage_file_get, storage_read), so an agent cannot tell which listing tool is the right one from the description alone.

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?

There is no guidance on when to use this versus storage_list, storage_file_get, or storage_read, and no stated preconditions. The single optional parameter hints at prefix-scoped listing, but the description never says so or explains when to supply it.

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