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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: that drafts are included and that this is the source as the editor sees it, which is context the annotations do 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?

Two sentences, no filler, with the return fields listed up front and the use case trailing. Tight, though 'Provides the current saved content' is somewhat redundant with the enumeration that precedes it.

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?

No output schema exists, so the description carries the return-value burden and does it well by naming the five fields returned. What is missing is explicit disambiguation from read_article, the closest sibling in a crowded article toolset.

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%, with both slug and productId fully documented (including provenance from list_articles/list_products). The description adds no parameter detail, so the baseline 3 applies.

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) and resource (help article), and it enumerates the returned fields (title, description, status, collection, Markdown body). The phrase 'as the editor opens it, drafts included' hints at the distinction from the sibling read_article, but it never names that sibling, so an agent must infer which article-reader returns published vs source content.

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 closing clause 'for reviewing or preparing an edit' implies when to reach for this tool, but there is no explicit when-not or alternative named. With a near-identical sibling (read_article) present, the lack of routing guidance is a real gap.

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