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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and scope. The description adds valuable behavioral context: it notes that the 'config' page reflects the instance's actual running knobs, implying dynamic data, and specifies that patterns covers multi-agent choreographies. This goes beyond the annotations, though it doesn't detail output format or potential size.

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 a single, dense sentence that front-loads the purpose and then delivers compact definitions for each page. It is efficient but slightly run-on; it could be broken into a list for readability, yet it avoids redundancy and earns its length.

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 tool with one parameter and no output schema, the description covers most functional aspects: what each page contains, the dynamic nature of config, and a usage fallback. However, it omits 'skill' from the parameter definitions and does not state the return format (e.g., text, markdown), which an agent might need. Given the tool's simplicity, the missing value and output format are notable gaps.

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 has a single enum 'page' with 6 values and zero descriptions. The description explains 5 of the 6 enum values (manual, patterns, interop, auth, config) but omits 'skill' entirely. This leaves a significant gap for an agent that might choose 'skill' without understanding its contents, so it only partially compensates for the schema's lack of documentation.

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: 'Fetch the service's own documentation.' It clearly delineates the tool's role from sibling tools (which are actions like claim_room, say, etc.) and gives a distinct purpose. The description also enumerates the documentation pages, making the scope unmistakable.

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 states, 'Use this for anything these tools do not cover,' which directly tells the agent when to select this tool over its siblings. It also implies the documentation is a fallback for unsupported operations, providing unambiguous selection criteria.

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