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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description corroborates them by spelling out that the draft's existing content is replaced and component ids change. It adds context the annotations cannot carry: the draft stays invisible to visitors until publish, the etag gives stale_draft protection, and the template must be re-read afterwards because ids and structure shifted.

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 operative instruction is front-loaded in the first sentence, and the rest is organized around when-to-use, state safety, and return behaviour. The middle paragraph on template anatomy (six page kinds, six regions) is longer than strictly needed for invoking this tool and slightly dilutes focus.

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 destructive, open-world mutation with no output schema, the description covers the essentials: what is overwritten, that nothing is published, the v1 rejection path, the stale-draft guard, and what the call returns (applied sections, warnings, new status with etag). Little an agent needs to call it correctly is missing.

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 the baseline is 3; the description still earns a bump by explaining the consequence of omitting `sections` (everything replaced, ids change) and by framing `etag` as a stale-state guard. The theme and sections semantics largely restate the schema, keeping it out of 5 territory.

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?

Opens with a specific verb and resource ('Start the draft from a ready-made theme') and maps it to the concrete dashboard operation ('Compare & apply'), then immediately distinguishes whole-theme copy from partial-section copy. An agent can tell this apart from helpcenter_copy_template_region or helpcenter_add_template_components without opening a schema.

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?

Gives an explicit decision rule: omit `sections` to take the entire theme, or name specific sections (with a concrete example list) to borrow only the look. It also states the v2-only precondition and the template_migration_required failure mode, and routes follow-up work to the design edit tools and helpcenter_publish_template.

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