Save to Canva

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

Beyond the annotations, the description discloses that images become new editable designs while videos only land in Uploads, that the call is free, that Canva must be connected via Settings > Connectors > Canva, and that each design's edit link is returned. It does not explicitly warn that repeated calls create additional designs/uploads (non-idempotent), which would fully close the behavioral gap.

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 paragraph is dense but front-loaded with the core action and input sources, and every parenthetical adds useful routing information. It could be slightly easier to scan with bullets, but there is little wasted text.

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 5-parameter, no-output-schema upload tool, the description covers prerequisites (Canva connection), input forms, image vs video behavior, folder selection, and the returned edit link. Remaining gaps are minor, such as duplicate-call behavior and error cases.

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, but the description adds cross-tool meaning: ids come from list_library, folderId from list_canva_folder or create_canva_folder, asDesign:false means upload only, and title is optional. These details go beyond the schema text and help the agent source valid values.

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 and resource: send Hermoso renders to the user's Canva, uploading images as new editable designs and videos as uploads. It clearly distinguishes itself from sibling save/export tools such as save_to_drive, save_to_onedrive, and list_canva_designs by naming the Canva Uploads/design creation behavior.

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?

It explicitly names accepted inputs (Library ids from list_library, Hermoso render links, or any public https image/video link), routes local files through upload_file, points folder selection to list_canva_folder/create_canva_folder, and explains asDesign:false for upload-only behavior. This gives the agent clear alternatives and selection conditions.

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