cm_create_template

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

Annotations are minimal (only title), so the description must cover behavioral aspects. It indicates mutation ('create') but does not disclose effects, error conditions, or requirements like authentication. The input format is clarified, but more transparency is needed for a creation tool.

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 of 16 words, conveying all key elements efficiently. It is front-loaded and concise with no unnecessary information.

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 4 parameters and no output schema, the description does not mention return values, error scenarios, or prerequisites. It is incomplete for a creation tool, leaving uncertainty about what happens after successful creation.

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 baseline is 3. The description adds context by referencing 'hosted HTML' and 'optional ZIP of assets', corresponding to HtmlPageURL and ZipFileURL, but does not significantly enhance understanding beyond the schema.

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 verb 'Create' and resource 'template for a client', and specifies the input sources 'hosted HTML (and optional ZIP of assets)'. It effectively distinguishes from siblings like cm_copy_template and cm_update_template.

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 implies this tool is for creating new templates, but does not explicitly provide guidance on when to use it vs. alternatives such as cm_copy_template or cm_update_template. No exclusions or context are given.

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