Fetch the complete content of a documentation page. Use this after searching to get the full markdown content of a specific page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full URL of the page to fetch (e.g., "https://docs.example.com/docs/getting-started") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description accurately describes the behavior (fetching complete markdown content) and does not contradict any annotations (none provided). It lacks mention of potential constraints like rate limits or size, but is adequate for a simple read operation.
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 sentences, front-loaded with the core purpose, followed by usage guidance. No wasted words.
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 tool with one parameter and no output schema, the description sufficiently covers usage context (after searching) and return value (full markdown content).
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% (single parameter 'url' with clear format and example). The tool description does not add significant meaning beyond the schema, so baseline 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?
Clearly states the tool fetches 'complete content' of a documentation page, and distinguishes from the sibling tool 'docs_search' by specifying it is used after searching to retrieve full 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?
Explicitly advises to use this tool 'after searching' and indicates it returns 'full markdown content', providing clear context for when it is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: searching documentation and fetching the full content of a specific page. No overlap exists.
Both tools follow a consistent `docs_verb` pattern (`docs_fetch`, `docs_search`), making it easy to infer their functionality.
Two tools is a minimal but reasonable set for a documentation server. Could theoretically include a tool to list top-level sections, but the current count suits the core search-and-retrieve workflow.
The toolset covers the essential operations: finding relevant pages and retrieving their full content. Minor gaps like listing all available pages or getting page metadata exist, but they are not critical.
