onedrive_write_file

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

With no annotations, the description carries the full burden. It states the tool writes/upload a file, implying mutation, but offers no details on side effects (e.g., overwrite behavior), permissions needed, or error conditions. Critical transparency is missing.

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?

At one sentence, the description is concise, but it is overly terse and lacks any structural breakdown (e.g., what to provide, behavior). It earns its place minimally but could be expanded without losing conciseness.

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 no parameters, no output schema, and a two-word description, the tool definition is extremely incomplete. For a write operation, one would expect details on file specification, content encoding, conflict handling, and response. The context provides no such information.

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 0 parameters, and description coverage is 100% by default, but the description adds no meaningful guidance on how to specify file content, path, or name. This is a major gap; a user/agent cannot infer how to provide the file data. Baseline for 0 params is 4, but the description fails to compensate, so score is reduced.

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 'Write or upload file to OneDrive' clearly identifies the tool's action (write/upload) and resource (OneDrive). It distinguishes from sibling tools like onedrive_read_file or onedrive_delete_file. However, it does not specify whether it supports overwriting or appending, which slightly reduces 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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like onedrive_move_file or when one would not use it. There is no mention of prerequisites or conditions.

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