Save file(s) to OneDrive

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

Annotations already indicate a non-read-only, non-destructive write operation. The description adds valuable extra context: it returns a webViewLink, requires OneDrive to be connected, and creates folders if new. This goes beyond the annotations and schema, though it doesn't cover error handling or duplicate-name behavior.

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 efficiently packs purpose, workflow, return value, and prerequisites. There is no filler or repetition, making it easy for an agent to parse quickly.

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 simplicity (4 params, no output schema), the description covers the necessary context: return value, prerequisites, and input handling. Minor gaps like explicit limits (up to 20 URLs, already in schema) and error behavior are not critical for successful invocation.

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 100%, so all parameters are documented. The description adds meaning by explaining the relationship between url and urls (singular vs. array) and the upload_file workflow, which clarifies when each parameter is used beyond the schema definitions.

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 states a specific verb ('Save') and resource ('Microsoft OneDrive'), and clarifies the scope ('a Hermoso render — or ANY file'). It clearly distinguishes from sibling operations like list/get/update/delete on OneDrive files, and from save_to_drive (Google Drive).

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?

Provides explicit guidance for different input types: pass a Hermoso render URL directly, or call upload_file first for local/external files. Also notes the optional folder (created if new) and the connection prerequisite. Doesn't explicitly name alternatives like save_to_drive, but the OneDrive-specific instructions are sufficient for correct selection.

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