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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine semantic context beyond them: what the id means (folder name and slug prefix), what title means (reader-facing only), and that the article count is of published articles only.

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?

Three sentences, front-loaded with the resource and returned fields, then the usage hook, then the id/slug semantics. The billing slug example is slightly verbose but directly disambiguates id, so it earns its place.

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 one-parameter, read-only list tool with no output schema, the description compensates by enumerating returned fields and explaining the two fields most likely to be misused (id vs title). Pagination or ordering behavior is unmentioned, which is the only real gap.

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% and the single productId parameter is already documented as coming from list_products. The description adds nothing further about the parameter, so the baseline of 3 applies; its added value lands in return-shape semantics rather than parameter meaning.

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 ('List') and resource ('help center collections') and enumerates the returned fields. The explanation that a collection id is a folder under docs/ and the first slug segment clearly separates it from article-level siblings like list_articles, search_articles, and create_collection.

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?

'Use it to decide where a new article belongs' gives a concrete trigger for calling it. It does not mention when not to use it or point at adjacent tools such as create_collection, update_collection, or list_products (beyond the productId reference), so it stops short of a full when/when-not treatment.

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