get-pages

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

Annotations already declare read-only and idempotent, but description adds valuable behavioral details: missing pages reported inline, content truncation at 50000 bytes with trailing marker listing sections, and followRedirects behavior. No contradiction with 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?

Three sentences, no wasted words. Front-loaded with main purpose in first sentence. Each sentence adds unique value (use cases, constraints, alternative).

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?

Covers input limits, output behavior (missing pages, truncation), and alternatives. Lacks explicit output schema but describes key aspects. Appropriate for a read tool with good annotations.

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 100%, but description adds contextual meaning beyond definitions: limit of 50 titles, explanation of truncation and section marker, and detailed followRedirects behavior. Enhances understanding without redundancy.

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?

Specific verb 'Returns' with clear resource 'multiple wiki pages' and options for source or metadata. Distinguishes from sibling 'get-page' by stating its use for single page or HTML, and lists use cases (reading cluster, diffing, syncing). Strong differentiation.

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 when to use: for multiple pages and specific use cases. Provides alternatives: 'For a single page or HTML output, use get-page'. Also covers constraints (50 titles, inline missing pages) and truncation behavior with section workaround.

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