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

Goes well beyond the annotations: it discloses per-call cost ($0.01), that failures are free, and that the collection's address is stable across renames. What it omits is whether an update is a partial merge or a full replace over the optional fields, and whether any permission level is required.

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 dense sentences, front-loaded with the create/update rule, followed by the field list, the address-stability note and pricing. No filler at all.

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 5-param mutation with no output schema, it covers cost, failure billing, slug stability and mode selection. The notable gap is return behavior — an agent creating a collection needs to know an id comes back to then call help_center_save_article.

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 0%, so the description must carry the semantics — and it mostly does, mapping all five parameters (id as create/update switch, name, one-line description, icon constrained to the design guide list, order among collections). It still leaves ambiguous whether omitting a field on update clears it.

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 pair and resource ('create a collection (no id) or change one (id)') and enumerates the mutable fields (name, description, icon, order). The create-vs-update split cleanly separates it from delete/list siblings, though no sibling is named explicitly.

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 'no id / id' conditional gives explicit when-to-use context for the two modes, which is real guidance. However, it never names alternatives an agent would need (help_center_list_collections to find an existing id, help_center_design_guide to source the icon), so the routing is only implied.

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