canvas_load_template

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether loading a template replaces or merges with existing canvas content, whether the action is undoable, or what permissions/preconditions are required for a clearly mutating operation.

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?

A single front-loaded sentence with the verb and resource first, followed by illustrative examples. The examples are somewhat long but they earn their place by showing the identifier space; nothing is redundant.

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 simple one-parameter tool with no output schema, the description is minimally sufficient. However, the key behavioral question for an agent — whether the current canvas is replaced or preserved — is left unanswered, which matters for a mutation tool with no annotations.

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% and there is only one required parameter, so the schema already documents templateId adequately. The example identifiers ('social-launch', 'youtube-thumbnail', etc.) add mild value by hinting at the naming convention, but no enum or format rule is stated, so baseline 3 is appropriate.

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?

Names a specific verb and resource ('Loads a pre-designed layout template onto the canvas'), which is unambiguous and distinct from the sibling templates_list (which enumerates rather than applies templates). It stops short of explicitly contrasting itself with siblings like canvas_create_new or templates_list, so it falls just 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?

No when-to-use or when-not-to-use guidance is given. The description never says where templateId comes from (presumably templates_list) nor when to prefer loading a template over canvas_create_new. Usage can only be inferred from the verb.

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