Select Template

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

With no annotations provided, the description must disclose behavioral traits, but it only states a high-level action. It does not indicate whether the operation is read-only, whether it has side effects, what it returns, or any required setup. This leaves the agent without important behavioral context.

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 sentence, making it compact and easy to parse. However, its brevity borders on under-specification, so it loses one point for lacking structured detail.

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 has 5 parameters, no output schema, and no annotations, yet the description provides no additional context about how 'the brief' is used, what the selection process entails, or how the result is returned. This is extremely incomplete for a tool with this complexity.

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 schema has zero documentation for its 5 parameters, and the description does not compensate by explaining any parameter meanings. Terms like 'style', 'audience', 'brandKitId', and 'aspectRatio' are left undefined, so the agent has no semantic guidance for filling them correctly.

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 a specific verb ('selects') and resource ('Canva template'), indicating the tool's function. However, it does not explicitly differentiate itself from sibling tools like list_brand_templates, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'for the brief' implies a use case, but it does not describe prerequisites or mention any sibling tools that could be alternatives, leaving the agent without decision support.

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