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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds context they cannot carry: the data comes from the "free editorial layer" (a tier/access distinction that matters alongside check_access/get_payment_info siblings) and that the response includes a full Markdown body, implying a potentially large payload. It doesn't mention size limits or failure modes for unknown ids.

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: the first front-loads what is returned, the second is a routing pointer. Nothing redundant with the title or schema.

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 no output schema, the description does the work of describing the return shape (metadata + article rows + pillar body), which is the essential gap. Minor omissions remain around payload size and behavior for a nonexistent cluster id.

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?

One required parameter with 100% schema description coverage including a concrete example ("rag-in-production"), so the schema already carries the semantics. The description only implies that cluster ids come from list_articles and adds no format or validity detail beyond that, so 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?

States a specific verb (fetch) and resource (one guide cluster / topic bundle) and enumerates the returned payload: cluster metadata, member article rows with Markdown URLs, and the pillar's full Markdown body. That detail distinguishes it from get_article and list_articles without needing to open any schema.

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 list_articles to discover cluster ids" gives an explicit prerequisite/orientation step and points at a sibling. It stops short of saying when to prefer get_article (single article) or get_corpus over this, so coverage is clear-but-not-exhaustive.

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