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

Goes well beyond the annotations: draft-vs-live semantics, the synced-region effect (removal applies to every page), visitor impact until publish, the v2-only restriction with the template_migration_required response, and the stale_draft refusal when the etag is out of date. It also flags all-or-nothing application, which annotations alone (destructiveHint/idempotentHint) would not 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?

Front-loads the operation and the draft/publish constraint, then separates arguments and returns into scannable blocks. A few sentences (e.g. the etag note) duplicate schema text and could be trimmed without losing meaning.

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 mutation with no output schema, the description covers lifecycle (draft vs published), side effects, failure modes, recovery options, and even summarizes the return payload. An agent has everything needed to call it safely and to instruct the customer afterwards.

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 adds the provenance of ids (from helpcenter_get_template) and explains why `page` exists (an unsynced region holding the id on multiple pages). It largely restates the etag and array semantics already documented in the schema, keeping it short of a 5.

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 ("Remove components from the draft") plus the key scope detail that nested children go too. It is clearly distinguishable from helpcenter_add_template_components, helpcenter_move_template_components, helpcenter_update_template_components and helpcenter_remove_template_css/script.

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 explicit when/when-not guidance: edits only the draft, nothing reaches visitors until helpcenter_publish_template, and publish only when the customer asks. It also names the alternatives for reversing the action (helpcenter_add_template_components or helpcenter_discard_template_changes) and the prerequisite source of ids (helpcenter_get_template).

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