canva_upload_asset

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no mention of required Canva auth, file size/format limits, whether the upload is additive or can overwrite, or what happens on failure. 'Upload' implies a write/mutation, but that is the only signal.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere.

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 write tool with no annotations, no output schema, and zero parameter documentation, the description is too thin. An agent cannot tell what file types are accepted, how the asset is named, or what the result looks like after upload.

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 0%, and the description never addresses the two parameters. It hints that the file must be a local image/video/audio path, which loosely informs file_path, but says nothing about the optional name parameter or that it defaults to null.

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 (upload) and resource (local image/video/audio file into the Canva media library), so the agent knows exactly what happens. It does not differentiate itself from nearby siblings such as canva_import_file or canva_import_url, which is the only gap.

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?

There is no guidance on when to choose this tool over canva_import_file or canva_import_url, no stated prerequisites, and no exclusion conditions. The agent is left to infer the distinction purely from the name.

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