canva_import_file

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

With no annotations, the description carries the full behavioral burden and mostly does not. It discloses the conversion outcome (becomes an editable design) but says nothing about authentication, size/page limits, whether the import is synchronous, failure handling, or where the resulting design lands. For a mutation-style upload tool this is a significant 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?

A single front-loaded sentence with no filler; the verb, input constraint, and outcome come in that order. It is efficient, though arguably terse given the complete absence of schema documentation.

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?

There is no output schema and no annotations, and 0% of parameters are documented in the schema, so the description is the only guidance the agent gets. It covers formats and the end result but omits the optional title parameter, input constraints, and any behavioral caveats, leaving the agent under-informed for a file-import operation.

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%, so the description must compensate. It clarifies that file_path is a local path and which extensions are accepted, which is real value, but it never mentions the optional 'title' parameter or how the design name is derived when title is omitted.

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?

States a specific verb (import), the resource (a local file), the accepted formats, and the outcome (a new editable Canva design). The word 'local' implicitly separates it from canva_import_url, but no sibling is named explicitly, so it stops short of full sibling differentiation.

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?

Usage is only implied: 'local ... file' hints that canva_import_url is the alternative for remote files, and the formats list tells the agent what inputs are valid. There is no explicit when-to-use/when-not-to-use statement, no prerequisites, and no mention of alternatives.

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