get_pages

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

The description states the tool lists pages, implying a read-only operation. However, annotations set destructiveHint=true and readOnlyHint=false, contradicting the description. The description does not acknowledge this contradiction or clarify any potential side effects.

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 succinct sentences. The first states the action and output; the second provides context. No unnecessary 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?

For a simple listing tool with no output schema, the description adequately describes the output (IDs and names). However, the contradiction with annotations reduces completeness since an agent cannot fully trust the description.

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?

No parameters exist, and schema coverage is 100%. The description does not need to add parameter information, so it performs adequately.

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 clearly identifies the tool's action (list all pages) and the resource (document), and distinguishes it from the sibling tool get_document by calling it a 'lightweight alternative'.

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 says 'Lightweight alternative to get_document,' implying when only page IDs and names are needed, use this instead. Lacks explicit when-not-to-use scenarios, but the alternative is clear.

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