confluence_get_pages_in_space

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

With no annotations, the description discloses key behaviors: pagination with cursor, default trimming of response (drops _links, _expandable, body content), and the full flag for raw response. It does not mention rate limits or auth, but the core behavior is well-covered.

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 sentences with no wasted words. First sentence states the purpose, second explains key behaviors. Perfectly front-loaded and concise.

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?

The description covers the essential behaviors for a paginated list tool: explaining cursor, default trimming, and the full flag. While it doesn't detail the response structure (no output schema), the trimming description gives sufficient context for typical 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?

Schema description coverage is 100%, so the baseline is 3. The description adds context on pagination and trimming behavior but does not elaborate on individual parameters (e.g., depth, bodyFormat) beyond what the schema already provides.

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 in a specific space' with a specific verb and resource, and the name distinguishes it from siblings like 'confluence_get_pages' and 'confluence_get_blog_posts_in_space'.

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 implicitly indicates usage context by requiring a spaceId and explaining pagination, but it does not explicitly state when to use this tool over alternatives like 'confluence_get_pages' (cross-space) or 'confluence_get_blog_posts_in_space'.

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