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

Annotations only indicate non-read-only, non-idempotent, non-destructive. The description adds critical behavioral context: it mentions the prerequisite ('Needs OneDrive connected'), the side effect of folder creation if new, and the return value ('Returns the OneDrive file(s) with a webViewLink'). This goes beyond the sparse annotations and fully discloses relevant behavior with no contradictions.

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 paragraph of four sentences, tightly packed with essential information. It leads with the core purpose, immediately clarifies the two usage modes, and ends with the prerequisite. No redundant or filler sentences; every clause contributes to correct invocation.

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 moderate complexity (4 optional parameters, no output schema), the description covers all critical aspects: source types, the upload_file dependency, folder creation, return value (webViewLink), and setup prerequisite. It also implies error context through the explicit connection requirement. There are no obvious gaps that would mislead an agent.

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 covers all parameter descriptions (100%), so baseline is 3. The description adds semantic value by explaining the workflow: how url vs urls[] map to render vs. multiple, and the required integration with upload_file for local files. It also clarifies the folder behavior ('created if new'), which is slightly more detailed than the schema. This elevates it above baseline but isn't exhaustive—e.g., it doesn't explain default naming if 'name' is omitted, though that's minor given schema coverage.

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 ('file(s) into the user’s connected Microsoft OneDrive'). It clearly distinguishes from siblings like save_to_drive by explicitly naming OneDrive and by describing the two supported source types (Hermoso render URL or pre-uploaded local file). It also names the relevant alternative (upload_file) for local files, making the purpose 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?

The description provides explicit when-to-use guidance: pass a Hermoso render URL for direct saves, and for local/external files, instructs calling upload_file first and passing the returned URL. It also notes the optional folder with auto-creation and the need for OneDrive connectivity. This is a clear usage path with an explicit alternative (upload_file), satisfying the 'when/when-not/alternatives' criterion.

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