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

The readOnlyHint annotation already signals safety. The description adds meaningful context by stating it returns raw markdown source rather than rendered content, which is useful and not redundant with the annotations.

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 two crisp sentences, front-loaded with the core action and followed by a useful prerequisite. No wasted words.

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 single-parameter APIable, the description supplies enough context: what is returned, how to find valid paths, and the scoped nature of the operation. A small gap is not clarifying behavior for invalid paths, but this is not critical for basic use.

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 the path parameter well, so the baseline is 3. The description adds helpful context about the parameter by directing users to list_docs first to discover valid paths.

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 begins with a specific action and object: 'Return the full markdown source of one Wraps page.' This clearly identifies what the tool does and distinguishes it from the sibling list/search tools by emphasizing singular page retrieval.

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?

It provides clear practical guidance: 'Call list_docs first to see which paths have markdown.' This strongly implies when to call this tool, though it does not explicitly contrast with search_docs.

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