canva_create_design

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

There are no annotations to carry the behavior burden, and the description only says 'crea un nuevo diseño.' It does not disclose whether the design is persisted immediately, whether authentication is required, what the return value is, or how the assetId customWidth parameters behave after creation. The verb implies mutation, but little else is transparent.

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 one concise, front-loaded sentence with useful examples and no redundant filler. Every part contributes to understanding the tool's purpose and scope.

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?

The tool is a creation operation with no output schema and no annotations, yet the description does not explain what happens after creation, what the result looks like, or how custom dimensions actually work. It mentions 'dimensiones personalizadas' but the schema only has customWidth, with no customHeight, which leaves an important gap. A richer description is needed for an agent to call this correctly.

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 documents every parameter, including title, assetId, presetName, and customWidth, so schema coverage is high and the baseline is 3. The description adds a small amount of meaning by listing preset examples and mentioning 'dimensiones personalizadas', which maps to customWidth, but it does not add meaningful parameter semantics beyond the schema.

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 and resource: 'Crea un nuevo diseño en Canva' (creates a new design in Canva), and gives concrete examples such as presentation, document, Instagram post, flyer, banner, or custom dimensions. This clearly distinguishes it from sibling tools like canva_list_designs, canva_get_design, and canva_upload_asset.

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 purpose is clear enough that an agent can infer this tool is for creating new designs, but the description does not explicitly state when to use it versus alternatives or mention any exclusions. No sibling tools are referenced, so routing partly depends on the agent's own reasoning from the obvious resource difference.

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