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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds non-trivial context beyond that: the default output is a summary and the full body is 'still capped', which tells the agent about truncation behavior. The cryptic '[no key]' note adds little clarity.

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 short sentences that are front-loaded with the resource identifier forms; almost no waste. The trailing '[no key]' fragment is ambiguous and slightly detracts from an otherwise tight statement.

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?

An output schema exists, so return-value detail is not required. For a read-only single-item fetch, the description covers identifier forms, default behavior, and the full-body toggle adequately; the remaining gap is sibling disambiguation rather than missing mechanics.

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?

With 0% schema description coverage, the description compensates well by explaining the three accepted identifier forms (path, slug, full URL) for path/slug and the meaning of full (body vs summary). It does not address precedence when both path and slug are supplied, nor the schema's length limits.

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 and resource ('Published article for a path, a slug, or a full URL') and clarifies that the default return is a summary. It distinguishes itself somewhat from list_articles/search_articles by being a single-item fetch, but does not address the nearly identical get_article_summary or get_article_section siblings, leaving an agent to guess which one to pick.

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?

Provides some invocation guidance ('The default is a summary. Set full to true for the body'), which is useful for choosing output depth. However, it gives no explicit when-to-use vs get_article_summary, get_article_section, or related_articles, so the choice among close siblings is left to inference.

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