Create Autofilled Presentation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'creates' a design, but omits critical details such as potential async execution (hinted by the waitForCompletion parameter), side effects, authorization requirements, or risk profile. This is a significant transparency gap for a mutation 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, front-loaded sentence with no filler words. It efficiently conveys the core action and resource, making it easy to parse and remember. The brevity is appropriate for a tool whose complexity is not matched by the description, but the sentence itself is well-structured.

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?

Given 4 parameters, nested objects, no output schema, and no annotations, the one-sentence description is inadequate. It fails to explain the data contract, the role of the 'title' parameter, whether the operation is asynchronous, or how this tool relates to sibling tools. A minimal viable description for this tool would require more context to ensure correct 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 description coverage is 0%, so the description must compensate. It gives partial meaning to 'brandTemplateId' and 'data' via 'brand template' and 'Autofill data,' but does not explain the purpose or format of 'title' or 'waitForCompletion.' The 'data' object's structure is also unspecified, leaving important parameter semantics unresolved.

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 tool creates a Canva design from a brand template using Autofill data. This specific verb+resource+method distinguishes it from sibling tools like create_presentation or generate_presentation_from_brief, which do not involve Autofill data or brand templates.

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 the use case of filling a brand template with Autofill data, but it does not explicitly state when to prefer this tool over alternatives like create_presentation or apply_brand_kit. There is no mention of prerequisites, exclusions, or when not to use it, so the guidance remains implicit.

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