Get Brand Template Dataset

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

With no annotations, the description carries the full burden. It only says 'returns' the fields, implying read-only behavior, but does not disclose potential errors, authentication requirements, or any other side effects. The output structure is also unspecified.

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, concise sentence that front-loads the purpose ('Returns...') and contains zero wasted words. It is appropriately sized for the tool's simplicity.

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 the tool has only one parameter and no output schema, the description is minimally complete for a basic get operation. However, it lacks any context about how the returned dataset fields are meant to be used, such as in autofilling presentations, which would be helpful.

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 single parameter brandTemplateId is referenced in the description as 'a Canva brand template', which adds a bit of context beyond the schema's bare property name. However, the description doesn't explain where to obtain the ID or any format requirements, leaving the 0% schema coverage partially uncompensated.

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 returns 'the autofillable dataset fields for a Canva brand template', using a specific verb and resource. This distinguishes it from siblings like list_brand_templates (which lists templates) and create_autofilled_presentation (which consumes the dataset).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that it's a prerequisite for create_autofilled_presentation or any other contextual usage.

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