Read a documentation page

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

Annotations already provide readOnlyHint, openWorldHint, and destructiveHint. The description adds behavioral detail on output (page title, URL, version, complete markdown including code samples) and notes that anchors are ignored, which goes beyond the annotation. No contradictions exist.

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 moderately long but each sentence serves a purpose: defining the action, providing usage guidance, describing output, and stating restrictions. It avoids redundancy, though it could be slightly tightened without losing clarity.

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?

The description gives complete context: when to use (after search_docs), what it returns (full markdown with code samples), and what not to use it for (finding pages, external domains) with explicit pointers to alternative tools for other domains. No critical information 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?

Schema description coverage is 100% for both parameters, with examples for url and a clear enum with default and matching guidance for version. The tool description itself adds no further parameter-level meaning beyond what is already in the schema, so a baseline of 3 is appropriate.

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 reads a full documentation page, with a specific verb ('read') and resource ('single page of the official Capacitor documentation'). It explicitly distinguishes itself from sibling tools like 'search_docs' (which finds pages) and the list_* tools (which list content).

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 explicitly instructs using this tool after 'search_docs' and provides clear exclusions: 'Do not use this to find a page' and 'Do not use it for pages outside capacitorjs.com', with alternative tools for other domains. This leaves no ambiguity about when to choose this tool over siblings.

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