get_doc_page

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

No annotations exist, but the description clarifies it's a read operation ('Get') and defaults to markdown. It doesn't detail error handling or limits, but for a simple fetch tool this is acceptable.

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 with no filler. The first sentence covers purpose and default output; the second adds usage ordering. Every word earns its place.

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 fetch tool with comprehensive schema descriptions, this description covers the essential flow (use after listing, returns content). No output schema is needed for clarity.

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%, so baseline is 3. The description adds the default content_format ('text/md'), which is helpful but overlaps with schema descriptions. No critical param info is missing.

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 explicitly states the action (Get a single page), the resource (Doc), and the output format (markdown default). It distinguishes from sibling 'get_doc_page_listing' by mentioning it should be used after listing to read one specific page.

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 directly advises using this tool after 'get_doc_page_listing', providing clear sequencing. While it doesn't cover exclusion cases or alternatives, the context is sufficient for typical usage.

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