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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds useful context that documents are addressable by id via get_doc, but it does not describe return shape, ordering, or pagination behavior; with strong annotation coverage, a 3 is appropriate.

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 short sentences cover the tool's scope and the key alternative workflow. The content is front-loaded with the documentation topics and ends with the actionable routing to get_doc, with no wasted wording.

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 no-parameter discovery tool with read-only annotations and no output schema, the description provides enough to understand the domain and the follow-up read operation. It would be slightly stronger if it explicitly stated that the list returns documents with ids, but the reference to using an id with get_doc makes that sufficiently clear.

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 tool has zero parameters, so there are no parameter meanings to explain beyond the schema. The baseline for a zero-parameter tool is 4, and the description does not need to add parameter semantics here.

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 identifies documentation pages and enumerates the covered domains (installation, configuration, API, webhooks, AI providers, MCP, n8n), so the agent knows exactly what resource this tool exposes. It also distinguishes the tool from get_doc by explaining that get_doc reads an individual document by id.

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?

It explicitly routes the agent to get_doc when it wants to read one document by id, which clearly separates listing from reading. It does not explicitly say 'use list_docs to discover available documentation', but that use is strongly implied by the enumeration and the contrast with get_doc.

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