get-files

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

No annotations are provided, so the description must disclose all behavioral traits. It adequately discloses the sorting order, but does not mention absence of side effects, authentication requirements, handling of empty results, or pagination behavior beyond the limit parameter. The description adds the key sorting behavior but leaves other aspects unspecified.

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 brief and front-loaded with the core purpose. However, the second sentence restates the sorting order (descending already implies most recent first), which is slightly redundant; otherwise it is well-structured.

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?

This is a simple list operation with no output schema. The description covers the basic behavior and sorting, but does not explain the effect of the 'includes' parameter on the response, return object fields, or behavior when no files exist. Given the tool's simplicity and schema coverage, it is adequate but not fully complete.

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 input schema already provides descriptions for both parameters (limit with constraints and default, includes with enum). The description does not add any additional meaning or guidance for parameters, so it adds no value beyond the schema.

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 the specific verb 'Returns', names the resource 'list of file objects', and adds a distinct sorting behavior (last updated descending). This clearly distinguishes it from sibling tools like get-file-by-id or add-file.

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 a list of files, but does not explicitly state when to use it over alternatives such as get-file-by-id, nor does it mention exclusions or prerequisites. The usage context is clear but not elaborated.

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