files_list

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

No annotations are provided, so the description must fully disclose behavior. It states the list operation is read-only in tone, but it does not explain return format, pagination, ordering, default behavior when namespace is omitted, or any error/edge cases. This leaves significant behavioral gaps.

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, front-loaded sentence with no filler. Every word adds information: the operation, the resource, and the filtering capability. This is appropriately concise for a one-parameter listing tool.

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 no annotations, no output schema, and a 0% schema description coverage, the description is too sparse. It fails to mention what the response looks like, whether the result is a list of metadata or contents, or the effect of omitting namespace. While the tool is simple, the available context is insufficient for confident invocation.

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%, so the description must compensate. It does clarify that namespace is an optional filter, which adds some meaning, but it does not explain valid namespace values, default behavior when omitted, or how filtering behaves. The meaning is barely more than the parameter name provides.

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 clear verb ('List') and a specific resource ('uploaded files'), and notes an optional namespace filter. It does not explicitly contrast with sibling tools like file_upload or files_types, but the resource and action are specific enough to avoid major 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 the tool is for retrieving uploaded files, optionally filtered by namespace, but it gives no explicit guidance about when to use it instead of related tools such as kvp_list, inspect_storage, or files_types. No exclusions or alternatives are mentioned.

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