Save file(s) to OneDrive

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

Goes beyond the annotations by explaining that the tool creates the folder if new, returns a webViewLink, and requires OneDrive to be connected. These are useful behavioral details. It does not clarify overwrite or duplicate behavior, but the disclosed traits add meaningful context.

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?

Three highly informative sentences with no filler. The core action, parameter usage, prerequisite, return value, and setup need are all packed efficiently. Every sentence 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?

For a tool with 4 simple parameters and no output schema, the description covers the important invocation details: what to pass, how to handle local files, return value, and auth prerequisite. The urls max count is in the schema, so no gap there. Slightly more detail about file naming or behavior on collisions would improve it, but it is largely complete.

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 coverage is 100%, so the baseline is 3. The description adds value by clarifying the relationship between url and urls (single vs several renders), explaining the upload_file workflow for local/external files, and noting the folder is created if new. This helps the agent understand the parameters beyond their schema descriptions.

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 clearly states the action: save a Hermoso render or any file to the user's connected OneDrive. It does not explicitly name sibling tools like save_to_drive, so it misses the top distinction point, but the verb+resource combination is unambiguous.

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 clear context: for local/external files, call upload_file first and pass the returned URL; for Hermoso renders, pass the render URL directly. It also notes the OneDrive connection prerequisite. It does not explicitly mention when not to use this tool versus save_to_drive or other OneDrive tools, but the guidance is strong.

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