Create Template Version

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

Annotations only indicate non-read-only, non-idempotent, non-destructive behavior. The description adds little beyond the creation action, omitting important behavioral context such as the effect of 'active' on the template's current version, auto-generation of plain content, or what response is returned. This is a meaningful gap for a mutation 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, front-loaded sentence with no filler. However, 'settings' is vague and could be more explicit, which slightly reduces structural payoff despite the overall compactness.

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?

With 8 parameters and no output schema, the description is minimal but not wholly inadequate because the schema documents each field. Still, it lacks context about versioning semantics, how active versions are managed, and what the caller should expect after creation, leaving notable gaps.

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 parameters are individually documented in the schema. The description's phrase 'HTML content and settings' adds no specific parameter meaning beyond that, and it does not help disambiguate nuanced fields like active, test_data, or generate_plain_content.

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?

Description states a specific verb and resource: 'Create a new version of a template'. This clearly distinguishes it from sibling tools like create_template or update_template_version, and it names the core payload ('HTML content and settings').

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 the tool is for adding a version to an existing template, but it gives no explicit when-to-use guidance or exclusions. It does not contrast with create_template or update_template_version, so the agent must infer when this tool is preferred.

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