get_doc_page

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

No annotations are provided, so the description carries the full burden. It states the operation is a 'fetch' which implies read-only, but does not explicitly declare no side effects, error behavior, or access requirements. For a simple fetch, this is adequate but not rich.

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 plus a compact args block with examples. No fluff; every sentence earns its place. The information is front-loaded and easy to scan.

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 tool's simplicity (two string parameters, no nesting) and the presence of an output schema (though not shown), the description is nearly complete. It lacks error handling and existence prerequisites, but these are not critical for a straightforward fetch operation.

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 0%, but the description compensates with concrete examples for both docset ('svelte-5') and rel_path ('docs.md' or 'runes/state.md'), adding meaning beyond the bare schema titles. This is helpful and clarifies expected formatting.

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 'Fetch the complete raw markdown of a specific documentation page' - a specific verb (Fetch) and resource (documentation page) with an explicit output format (raw markdown). This distinguishes it from siblings like list_docsets, search_docs, and sync_* 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?

The description provides examples for both arguments but does not explicitly state when to use this tool versus alternatives like search_docs or list_catalog. It implies usage for retrieving a known page but lacks exclusions or alternative naming.

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