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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds valuable context by specifying that the content includes links to related pages and that it returns complete markdown, beyond what annotations provide. However, it does not mention any caveats like potential size limits or error cases, which would be a minor gap.

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 compact and front-loaded, with the primary action stated first. Every sentence contributes purpose, usage context, or relationship to alternatives, with no filler or redundancy.

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 simple one-parameter interface, the description fully covers what the tool does, how to use it, and what to expect in the output. The lack of an output schema is compensated by the clear statement that it returns full markdown content with links.

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?

The schema covers 100% of the single parameter, but the description enriches it by specifying that the URL must be a full URL and gives an example. This adds practical meaning beyond the schema's generic 'The URL of the page to fetch'.

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 fetches the full markdown content of a documentation page, using the specific verb 'fetch' and identifying the resource. It also distinguishes itself from the sibling tool searchDocumentation, which returns only partial 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 explains when to use this tool ('when you have a page URL and want to read its content') and contrasts it with searchDocumentation, noting that getPage retrieves the complete page when more details are needed. This provides clear guidance for tool selection.

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