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

The description adds meaningful behavioral context beyond the annotations: the draft becomes the live rendering source for notifications/documents, the action requires explicit request, and specific permission scopes are needed. It does not contradict any annotation, and it explains more than the raw flags alone would convey.

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 compact and front-loaded: first the action and effect, then the trigger and permissions. Every sentence contributes useful information, and there is no redundant fluff or repetition of the tool name.

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 two-parameter, side-effectful action with no output schema, the description covers the core invocation requirements: what happens, when to do it, and what authorization is needed. It does not describe the return value or what happens to the previous live version, but those are not essential for correct invocation.

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 already fully documented. The description implicitly connects templateId to the draft and kind to notification/document kinds, but it does not add significant new semantic detail beyond the schema. 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?

The description names a specific verb ('Publish'), a specific resource ('a template’s draft'), and the concrete outcome ('making it the live version notifications and documents render from'). It is clearly distinguishable from siblings like update_template_draft and preview_* tools, and the analogy to publish_form reinforces the intended action.

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 clearly states that this action should only occur on explicit user request, which prevents an agent from auto-triggering it. It also gives a permission precondition with the required scopes. It does not explicitly enumerate alternatives, but the trigger and resource are clear enough for correct selection.

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