Save file(s) to Google Drive

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

Annotations indicate a non-read-only, non-idempotent, non-destructive operation, and the description adds substantial context beyond that: the return value is a Drive file with a webViewLink, Google Drive must be connected, and the drive.file scope restricts access to only files Hermoso created or the user explicitly shared. This is exactly the kind of behavioral disclosure that prevents misuse.

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 front-loaded with the core purpose, then proceeds through input modes, optional parameters, return value, and prerequisites. Every sentence adds operational value, including the scope warning, and none is redundant with the schema or annotations.

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 mutation tool with no output schema, the description covers inputs, parameter roles, return information, setup prerequisites, and access limitations. An agent has enough context to call it correctly and to avoid the common mistake of assuming full Drive access.

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 already documents all four parameters and covers them 100%, so the baseline is strong. The description adds meaningful semantics by explaining how url and urls[] relate to Hermoso render URLs, how to handle local/external files via upload_file, and that folder is created if new. This enhances, rather than merely repeats, the 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 states a specific action and resource: 'Save a Hermoso render — or ANY file — into the user's connected Google Drive.' It clearly explains both the single and batch modes and explicitly names the alternative workflow for local files. The destination (Google Drive) distinguishes it from sibling tools like save_to_onedrive and save_to_swipefile.

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 gives concrete usage context: when the input is a Hermoso render URL, pass it directly; for other files, call upload_file first and use its returned URL. It also spells out a required prerequisite (Google Drive connection) and a scope limitation. It does not explicitly contrast with OneDrive or Swipefile siblings, so it stops short of full when-not guidance.

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