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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral detail beyond annotations: output is Markdown with absolute links, screenshots are rendered as images with descriptive alt text, and marker lists explain numbered markers. This is valuable return-format context.

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 sentences, tightly front-loaded with what is returned, then input formats. Every sentence earns its place with no 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?

No output schema exists, but the description compensates by explaining the Markdown return format, link absolutization, and screenshot/alt-text semantics. Combined with 100% schema coverage and annotations, this is nearly complete; only pagination or size limits for very large pages are unaddressed.

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 description coverage is 100%, so the schema documents both parameters including the lang enum and its override/default behavior. The description adds format examples for the page parameter (URL, path, or slug) and an illustrative value, slightly exceeding the baseline of 3.

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+resource ('Returns one documentation page as Markdown') and clearly distinguishes itself from siblings by naming search_docs and list_pages as sources of the URL/path it accepts. This is precise and immediately actionable.

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 tells the agent where the input comes from (search_docs or list_pages) and gives concrete accepted formats with an example. It lacks explicit when-not-to-use guidance, but the sourcing relationship to siblings provides clear routing context.

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