canva_upload_asset

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not mention whether the upload overwrites existing assets, what happens on duplicate names, any size limitations, or whether authentication via canva_get_auth_status is required first. This is a significant gap for a mutation-like tool.

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, concise sentence that conveys the core purpose without unnecessary words. It is appropriately short and front-loaded with the action verb.

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 no annotations and no output schema, the description is too sparse. It lacks critical context such as whether the upload requires prior authentication (the sibling canva_get_auth_status suggests this might be needed), expected file formats, or what happens after a successful upload. An agent would have to rely on trial and error.

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 provides 100% coverage with clear descriptions for both 'name' and 'filePath'. The description adds no additional semantic value beyond what the schema states, so a baseline score of 3 is appropriate.

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 verb 'Sube' (upload) and the resource ('archivo de imagen o recurso local a Canva'). It distinguishes itself from sibling tools like export, list, and profile tools, though it could be more specific about what types of local resources are supported beyond images.

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 implies usage for uploading local files to Canva, which is distinct from the sibling tools. However, it provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites such as authentication or file format restrictions.

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