Read a Stablevoy documentation page

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds real context beyond that: the output is whole-page Markdown, non-Stablevoy addresses are rejected with a list of valid pages, and no API key is required. It stops short of mentioning size limits or truncation for very large pages, so it is not fully complete.

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?

Three tight sentences, front-loaded with what the tool returns before the routing advice and the security note. No filler or repetition; every clause carries usable information.

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 single-parameter read tool with full annotation coverage and no output schema, the description supplies everything needed: input forms, the alternative tool for discovery, refusal behavior, and the fact that no credentials are required.

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 100% and the schema's own parameter description already lists the same examples ('/docs/webhooks.md', 'openapi', 'errors') that the description repeats. The description adds only the framing that a path comes 'from search_docs,' which is mild value over an already-complete schema — baseline 3 applies.

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?

States a specific verb and resource ('Gets one whole page of the Stablevoy documentation') and names the return format (Markdown), which is what an agent needs before calling. It is clearly distinct from the sibling search_docs, which only finds pages rather than reading them.

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 routes the agent: 'Use search_docs first when you do not know which page has the answer,' and describes the shortcut values ('openapi', 'errors') for common lookups. It also states the boundary condition — only Stablevoy pages are read, other addresses are refused — so the agent knows what not to pass.

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