list_files

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

Since no annotations are provided, the description fully carries the burden. It details the return fields (ok, instance, dir, count, truncated, files), the 200-entry cap, sorting, and explains how files can be used by other tools (open_file, launch_app downloads). No behavior is left unclear.

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 paragraph that efficiently conveys the tool's purpose, return format, and usage context. It is front-loaded with the core function. Slightly dense, but every sentence adds value. Could be broken into bullet points for easier scanning.

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's role in a file management workflow, the description completely covers the return structure, limits, sorting, and relationships with siblings. The output schema exists, so return values are already documented; the description adds practical context for when and how to use the tool.

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 single parameter instance is implied by the phrase 'The instance's staging folder' but is not explicitly described. Schema coverage is 0%, and the description does not explain that instance is an integer ID. Some compensation occurs through context, but a direct explanation would improve clarity.

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 tool lists the instance's staging folder contents and returns a file list. It distinguishes itself from siblings like open_file, upload_file, and launch_app by explaining how files in the staging folder are used and how the tool fits into workflows.

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?

Explicit guidance is provided: call this after a download to confirm file arrival; browser uploads still go through upload_file. The description also notes the return structure with a 200-entry cap and sorting, giving the agent clear when-to-use context.

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