List Canva brand templates

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

Annotations already cover readOnly/idempotent/non-destructive, so the description's added value is the plan requirement, the 'read-only, free' cost signal, and the important disclosure that brandTemplateId changes the response from a list to a field/type inventory. It does not say whether other params (query, limit, continuation) are ignored in that mode.

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?

Three short sentences, front-loaded with the primary purpose, followed by the two mode modifiers. Nothing is redundant with the title or padded.

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 five-parameter read-only list tool with no output schema, the description covers purpose, prerequisite, cost, and the alternate response mode. What a returned page looks like and how continuation interacts with the other filters is left to the schema.

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%, so the schema already documents all five parameters. The description reinforces the two interesting ones (brandTemplateId, autofillOnly) and the mode switch, but adds no syntax, defaults, or interaction detail beyond the schema wording.

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 and resource ('The user's Canva brand templates') and clarifies the alternate mode triggered by brandTemplateId. It distinguishes the resource from neighbors like list_canva_designs or list_canva_folder implicitly by naming 'brand templates', though it never names a sibling explicitly.

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?

Gives concrete selection rules: pass brandTemplateId to get one template's autofill fields, use autofillOnly:true to list only templates with fields. It also states the plan prerequisite (Canva Pro, Teams or Enterprise), which prevents a doomed call, but offers no explicit 'not for X, use Y instead' routing against sibling tools.

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