publish_template

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

With no annotations, the description carries the full burden. It usefully discloses that publishing creates an immutable snapshot, which is a valuable behavioral trait. However, it omits permissions required, whether the operation is idempotent, what happens if the template is already published, and other side effects.

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 of nine words that conveys the action and its core consequence without any filler. Every word earns its place.

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 mutation tool with no annotations, no output schema, and two completely undocumented parameters, the description is too thin. It states the core behavior and immutability but leaves the agent without usage guidance or parameter meaning, which are needed to invoke it correctly.

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 0% for two parameters, id and alias, and the description does not mention either one. There is slight semantic value from the word 'template' implying a template identifier, but the agent receives no guidance on which parameter to use or what alias means.

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 states a specific verb and resource: 'Publish a template.' It also adds the key outcome, 'snapshotting an immutable version for sends,' which clearly differentiates it from sibling tools like create_template, get_template, and list_templates.

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 phrase 'for sends' hints at usage context, but there is no explicit guidance on when to publish versus create or get a template, no prerequisites, and no exclusions or alternatives named. The agent must infer the situation.

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