read_docs

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

Since no annotations are provided, the description carries the burden of transparency. It discloses that 'every lane is reachable with a plain GET,' implying a read-only, side-effect-free operation. It also explains the content of the manual and patterns pages. Minor gaps include not explicitly saying 'read-only' or describing the skill page, but the statement about GET is a strong transparency signal.

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 concise (two sentences) and front-loaded with the core purpose. Each sentence contributes: the first states what it does, the second explains the page types and usage. No superfluous content.

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 simple schema (one param, no output schema) and no annotations, the description is nearly complete. It covers the tool's purpose, the main page values, and usage context. The only omission is the 'skill' page's meaning, which leaves a small gap for a tool with only three enum options.

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 description coverage is 0%, so the description must compensate. It adds meaning to the 'manual' and 'patterns' enum values by explaining what they contain. However, it does not describe the 'skill' page, which is also a valid enum value. Since only one parameter exists and most values are covered, this is a solid score.

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 the tool's function with a specific verb and resource: 'Fetch the service's own documentation.' It also differentiates from sibling tools by explaining that it covers anything they do not, and it enumerates the specific pages (manual, patterns) with their contents.

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 for anything these tools do not cover.' It also provides context for selecting between manual and patterns pages. However, it does not explicitly list when-not-to-use or name specific alternative tools, only referring to 'these tools' collectively.

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