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

Annotations already cover read-only safety, but the description adds substantial context beyond them: edits target a DRAFT (the same one the dashboard editor opens) and nothing reaches visitors until helpcenter_publish_template; classic v1 help centers return template_migration_required; migration is the owner's dashboard decision; and specific errors 409 and 403 are named. It also notes the guide is generated from the live component registry and is always current.

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-loaded with the core purpose and the when-to-use rules, then the domain model, then args, returns and errors. Some material (topic enum explanation, component_types example) restates the schema, and the paragraph on the design model is dense, but every section carries useful information.

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?

There is no output schema, and the description covers the return format (markdown plus structuredContent, with the overview's extra context), the draft/publish lifecycle, the v1 restriction, and the failure modes. An agent has everything needed to call this correctly on first attempt.

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, but the description adds real meaning: it explains what 'overview' actually returns (this help center's languages, FAQ sections, uploaded fonts), that component_types is capped at 8 with examples, and that accepted component values come from the Template Editor and a near-miss guess is refused. Only the agent_key parameter is left entirely to the schema.

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 ('Learn what can be customized in a help center's design and exactly how') and enumerates the covered domains: the model, edit operations, components, theme tokens, CSS, scripts, navigation. It is clearly the reference/guide tool as distinct from the mutation siblings such as helpcenter_add_template_components or helpcenter_apply_template_theme.

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?

Explicit when-to-use rules: call with 'overview' before the first design edit in a conversation, and with 'components' plus component_types before adding or configuring a component. It also states the constraint that only v2 help centers can be edited and routes publication to helpcenter_publish_template, giving clear alternatives and exclusions.

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