files.list

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

No annotations are present, so the description carries full burden for behavioral disclosure. It fails to indicate whether this is read-only, what pagination style is used (though parameters suggest cursor-based with startsAfter), or what the return structure contains.

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?

Extremely brief (2 words), so not verbose, but the single sentence does not earn its place as it merely restates the tool name without adding value. Appropriately sized but empty of 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 4 undocumented parameters and no output schema, the description should explain filtering, sorting, and pagination mechanics. It fails to provide sufficient context for an agent to construct valid queries or understand the response shape.

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 coverage is 0% and the description provides no compensation. It does not explain what 'category' filters, what 'ascending' sorts by, that 'limit' caps results at 100, or that 'startsAfter' is a pagination cursor.

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 'List files' is a tautology that restates the tool name (files.list). While it technically states the action, it fails to distinguish from siblings like files.get (which retrieves a specific file) or files.create.

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?

No guidance provided on when to use this versus alternatives. The description does not clarify the difference between listing files (plural) versus getting a specific file (files.get) or creating files.

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