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 useful behavioral context by disclosing pagination limits (max 10 per page) and search by title/content, which goes beyond the structured info.

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 repetitive: the opening paragraph is duplicated in the 'When to use' section, and the parameter list mirrors the schema. This redundancy violates conciseness—content that should have been kept once is repeated, wasting space and reader attention.

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?

For a simple read-only fetch with safe annotations and complete schema, the description is adequate. It mentions pagination and search, but doesn't describe the structure of returned documents or error scenarios, which would be useful since no output schema is provided.

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 coverage is 100% with detailed descriptions for each parameter, so the schema already carries the meaning. The description duplicates these parameter explanations without adding new semantic detail, effectively providing no extra value beyond the schema.

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 'Get help and support documentation articles' with a specific verb and resource. It also mentions pagination and search, which gives a precise scope. While it doesn't explicitly contrast with siblings, the resource (documentation) is distinct from other fetch_* tools.

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?

There's a 'When to use' section but it merely restates the main description—'Get help and support documentation articles'—without providing exclusions, prerequisites, or alternatives. The usage is implied by the tool's purpose, but no explicit guidance for choosing this over other tools is given.

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