Files File Manager

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

Description claims 'Upload and manage files', implying write operations, but annotations have readOnlyHint=true, which indicates a read-only tool. This is a clear contradiction. No additional behavioral context is provided beyond the annotation.

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?

Description is concise (two sentences) but lacks essential details and is front-loaded with the purpose. However, it is too vague and does not earn its place due to missing information.

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?

Despite having an output schema and no parameters, the description is contradictory to annotations and fails to explain how the tool works or what its behavior is. It is not complete enough for an AI agent to use correctly.

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 has no parameters, and the description does not explain how to specify files for upload (e.g., via drag-and-drop). The phrase 'Drop files here' is insufficient for an AI agent to understand the mechanism.

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?

Description says 'Upload and manage files' which indicates a broad file management purpose, but 'manage' is vague and does not clearly distinguish from sibling tools like files_list_files which handle specific list operations. The purpose is somewhat clear but lacks specificity.

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 on when to use this tool versus alternatives such as files_list_files. The description does not provide context for appropriate usage or mention any prerequisites.

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