confluence_get_pages_by_space

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

The description adds useful behavioral context (content field is ADF JSON, spaceKey resolves internally), but does not mention pagination, ordering, or the limit parameter's effect. With no annotations, the description should disclose more about default behavior.

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, front-loaded, no wasted words. Efficiently covers purpose and key output detail.

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 list tool without output schema, the description omits pagination behavior and return structure. It partially compensates with the ADF JSON note, but the missing pagination info leaves agents guessing about limit usage.

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% (both parameters have descriptions). The description adds minor value by noting internal resolution of spaceKey and the content field format, but does not significantly enhance 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 the action ('Get pages'), the resource ('from a specific Confluence space'), and distinguishes itself from siblings like confluence_get_page (single page) and confluence_search_pages (search across spaces).

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 implies the use case (listing pages in a space) but does not explicitly compare to alternative tools (e.g., 'use this when you need all pages, not a search'). No when-not or exclusions are provided.

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