add-file

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

With no annotations provided, the description must carry full behavioral disclosure. It only states a high-level add operation, with no mention of whether it uploads binary data, requires authentication, returns a file ID, or handles existing files. This is critically insufficient.

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 short but under-specified. Being concise is not the same as being uninformative; this single sentence is too vague to serve as a useful tool guide.

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?

For a tool with two parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain required versus optional fields, expected return values, error behavior, or how the operation integrates with the rest of the API.

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 description coverage is 0%, and the description adds no parameter-level meaning. It does not explain the 'file' binary parameter or the 'folder' integer parameter beyond their names/titles, leaving the agent to guess their relationships and constraints.

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 'Adds a file object' essentially restates the tool name 'add-file' without specifying what the file is added to, what kind of file object is expected, or how it differs from sibling tools like add-page or move-file-to-location. It is a tautological restatement with no added clarity.

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?

There is no guidance on when to use this tool versus alternatives like move-file-to-location or get-files. No context, prerequisites, or scenarios are provided, so an agent has no basis for choosing this tool over others.

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