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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the return format (Markdown), which is genuinely useful, but says nothing about what happens with long pages, whether content is truncated, or authentication requirements.

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 short sentences, front-loaded with the action and return format, then the input guidance. Nothing is wasted.

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 rich annotations, this covers what the agent needs: what it returns, how to build the input, and why the sibling tools matter. The only gap is the ambiguity of 'one page' (pagination vs. truncation), which could affect how agents chunk large 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 coverage is 0%, so the description must carry parameter meaning — and it does: 'id' can be a path-style id from search/list_pages or a full page URL, with a concrete example of the format. It doesn't mention the 500-character limit or error behavior for invalid ids, but the dual input modes are clearly explained.

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 ('Return one page of the website as Markdown'), and names the sibling tools that produce valid input (search, list_pages). It stops short of explicitly contrasting this with those siblings, but the output-format detail makes the tool's job distinct.

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?

Clearly signals the prerequisite workflow: get an id from search or list_pages, then pass it here, with a concrete example ('/work/raubex'). No explicit when-not or exclusion cases are given, but the context for use is unambiguous.

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