Export Canva Presentation

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

Annotations give only readOnlyHint=false and openWorldHint=true, so the description must explain behavior itself. 'Kích hoạt tác vụ' hints at an asynchronous job, but it never says whether the call blocks, returns a job id to poll, or yields a download URL — a serious omission for a mutating export operation with no output schema.

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 the action and formats named first and no filler. It is lean, though the brevity comes at the cost of the behavioral detail 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?

With no output schema and no annotations covering results, the description should say what the export call produces and how to retrieve the file. Instead it stops at 'trigger a task', leaving the agent unable to know the outcome of a successful invocation.

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% and both parameters are documented in the schema, so the baseline of 3 applies. The description does add the format vocabulary, but it lists only PPTX, PDF and PNG while the schema enum also permits jpg, leaving a small inconsistency rather than added meaning.

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 names a specific verb (kết xuất / export) and resource (bản thiết kế Canva) and enumerates the output formats, so the agent can tell it apart from canva_export_slide_thumbnail or canva_get_design_info. It stops short of stating scope boundaries against the other export-adjacent siblings.

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 statement of when to use this versus canva_export_slide_thumbnail or canva_sync_to_cloud, and no prerequisites (e.g. requires design_id from canva_get_design_info or canva_list_workspace_designs). The only implicit cue is the word 'export', which is already in the name.

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