publish-templatePublish a template and automatically unpublish all others sharing its alias, ensuring only one published template per alias at a time.
Publish a template and automatically unpublish all other templates with the same alias. Only one template per alias can be published at a time.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Template ID (tem_xxx format). |
Changes observed during successful MCP inspections.
v2.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden and does so for the most important trait: publishing implicitly unpublishes other templates sharing the alias. That is exactly the surprise an agent must know before calling. It stops short of stating permissions, error conditions, idempotency, or what is returned.
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?
Two tight sentences with the action first and the critical side effect second. Nothing is wasted and the ordering is correct for an agent scanning for behavior.
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 one-parameter mutation with no output schema and no annotations, the description covers the essential risk. It would be complete with a note on return value or failure modes, but what is present is sufficient to call the tool 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?
The schema already documents the single 'id' parameter at 100% coverage, including the tem_xxx format. The description adds no further parameter meaning (e.g., what happens with an invalid or already-published id), so baseline 3 applies.
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?
States a specific verb and resource ('Publish a template') and immediately characterizes the operation's key semantic: alias-level exclusivity. This distinguishes it cleanly from siblings like update-template or create-template, which do not toggle publish state.
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?
Usage is implied by the verb — an agent knows to call this when it wants a template live. However, there is no explicit when-to-use/when-not, no mention of alternatives (e.g., update-template for field edits), and no prerequisites such as required template state or permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.