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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read nature is covered. The description adds transparency beyond annotations by specifying that it returns exactly 3 editor-curated documents, all known aliases, counts, related topics, and the page URL—details that clarify the tool's behavioral scope and completeness expectations.

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 two sentences, front-loaded with the core purpose ('An end-to-end overview of one management topic'), followed by a concise list of contents and usage guidance. Every clause provides useful information, with no redundancy or 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?

Given the tool's simplicity (1 parameter, no output schema) and existing annotations, the description fully covers what the tool returns and when to use it. It enumerates all return elements, provides a concrete example, and suggests an appropriate follow-up action, leaving no significant gaps for an agent to invoke it correctly.

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 provides a descriptive explanation for the 'topic' parameter, including aliases and a reference to list_topics, achieving 100% schema description coverage. The tool description does not add any additional parameter-level detail beyond restating that it works for 'one management topic,' so it meets the baseline but adds no extra 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?

The description clearly states that the tool provides 'an end-to-end overview of one management topic' and enumerates its exact contents (definition, explanation, 3 top documents, aliases, counts, related topics, URL). It distinguishes itself by advising to 'survey a discipline before going deep' and explicitly names 'search_content' as a follow-up, aligning with sibling differentiation.

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 description gives explicit when-to-use guidance: 'Use this to survey a discipline before going deep' and 'or to orient when the user describes a broad problem area.' It also provides a clear alternative/next step: 'Follow with search_content (topic filter) for the full catalog,' satisfying the requirement for alternatives.

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