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

Annotations already declare a safe read-only, closed-world call. The description adds substantial behavioral context beyond that: the answer is official and includes documentation links, must be displayed as written, and the model must not invent steps, UI paths, or setting names.

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?

Front-loads the core purpose, then usage scope, then exclusions, then output handling. Well structured, though it runs to four paragraphs and could be tightened slightly without losing meaning.

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?

Despite having no output schema, the description explains what is returned (an official Help Center answer with links) and how to present it. Combined with complete parameter coverage and annotations, nothing needed to invoke or use the tool correctly is missing.

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 100%, so both parameters (prompt and user_intent) are already documented in the schema. The description implies the input is a Canva product question but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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+resource: retrieve current, official answers to Canva product questions from the Canva Help Center. This is clearly distinguishable from every sibling tool, none of which are help/knowledge tools.

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?

Explicitly specifies when to use it (feature questions, settings, unexpected behavior, troubleshooting), when not to (design creation/changes, creative advice, non-Canva questions, capability questions), and the alternative behavior ('call this tool rather than answering from your own knowledge', and 'when no available Canva tool can directly complete the requested action').

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