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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: every guide is free to read (no auth/payment concerns) and the returned content exactly matches the human-facing page. No contradictions with annotations.

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?

The description is one tight sentence with a front-loaded return statement, followed by a compact list of known topics. Zero filler, every clause carries information.

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?

Given a single required parameter, an output schema, and annotations covering read-only/non-destructive behavior, the description supplies everything needed for a correct call: return structure, access context, and the full set of valid topic values. Nothing critical is missing.

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?

The schema already covers the topic parameter fully with an example slug, so the baseline is 3. The description adds a complete list of 8 known topic slugs, going beyond the schema's single generic example and giving the agent concrete valid inputs. This is meaningful added value.

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?

Description opens with a specific verb and resource: 'Returns one guide's full content (title, intro, sections)'. The clarifying phrase 'the same content the human page renders' further pins down the exact scope, and the enumerated known topics distinguishes it from siblings like list_guides or get_name without ambiguity.

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 usage context is clear: call this when you need the full content of a single guide, identified by its topic slug. The list of known topics helps the agent recognize valid inputs. However, it does not explicitly mention alternatives, such as using list_guides to discover additional topics, so it falls just short of full routing guidance.

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