confluence_get_pages

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

Discloses important behaviors: pagination (cursor-based), default output trimming (drops _links, _expandable, body content), and the ability to get raw response with full=true. No annotations provided, so description carries this burden well. Missing details on authentication or rate limits.

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: first states purpose, second covers pagination, third covers trimming and full parameter. No fluff, front-loaded with the core action.

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, and description does not explain the structure of the returned pages (fields, metadata). Lacks guidance on combining multiple filters and potential interactions. Incomplete for a 7-parameter tool without output schema.

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 has 100% description coverage with detailed parameter docs. The description adds global context (pagination, trimming) but does not significantly enhance individual parameter understanding beyond the schema.

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 states 'Get all pages' and explains filtering with various parameters, distinguishing itself from siblings like confluence_get_pages_in_space and confluence_get_pages_for_label which are more specific.

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?

The description gives pagination guidance ('use the returned cursor to fetch more pages') but does not explicitly compare with sibling tools or specify when to use this tool over alternatives. No exclusions or prerequisites mentioned.

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