list_files

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

With no annotations, the description carries the full burden of disclosing behavior. It only states 'List files' and does not mention that this is a read-only operation, whether it requires permissions, how pagination works, or what the response structure is. The description adds minimal behavioral context beyond the bare action.

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 that states verb and resource with no extraneous words. It is appropriately concise for a straightforward listing tool, and every word earns its place.

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?

The description is simple and the schema is rich, but for a tool with no annotations and no output schema, it lacks context about pagination behavior, usage guidance, and safety profile. It is minimally sufficient but leaves room for improvement in explaining when and how to use it effectively.

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 provides 100% coverage with descriptions for all four parameters (type, count, offset, folder_id), so the schema does the heavy lifting. The description adds no further parameter context, resulting in the baseline score of 3 for well-covered schemas.

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 in the Mailchimp file manager' uses a specific verb ('List') and a clear resource ('files in the Mailchimp file manager'), which clearly distinguishes it from sibling tools like get_file, upload_file, delete_file, and list_file_folders. It is unambiguous about the operation's scope.

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 usage for browsing files, but provides no explicit guidance on when to choose this tool over alternatives like get_file or list_file_folders, nor any exclusions or prerequisites. The context is clear enough, but no direct comparison or alternative is mentioned.

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