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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds the useful detail that the response is the full markdown body rather than metadata, but says nothing about unpublished/missing article behavior or errors.

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?

A single sentence that front-loads the verb, resource, scope ('one published article'), and lookup key, then supplies the format example. No filler.

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?

With both parameters fully documented and no output schema, the description adequately covers what is returned (markdown body) and how to identify the article. Only edge-case behavior for missing or unpublished slugs is unaddressed.

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 description coverage is 100%, so the baseline is 3, and the description lifts this by giving a concrete slug example ('billing/exporting-invoices') that demonstrates the collection-prefixed format required, which is more actionable than the schema's prose alone.

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?

Specific verb (read) plus specific resource (one published help center article) and even the return format (full markdown body). It does not, however, distinguish itself from close siblings like read_article_source or list_articles, which an agent must choose between.

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 word 'published' implicitly scopes usage to live articles versus drafts or source, and requiring a slug plus productId implies this is a lookup-by-identifier read. But there is no explicit statement of when to use this instead of read_article_source, list_articles, or search_articles.

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