get_space_pages

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

No annotations are present, so the description must convey behavioral traits. It indicates a read-only operation ('Get'), but it does not disclose that the 'limit' parameter prevents returning truly 'all' pages by default, nor does it mention pagination, authentication, or response format. This ambiguity is significant.

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?

The description is a single, concise sentence that gets straight to the point without any filler or redundant information.

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 tool with two parameters and no output schema, the description provides a basic understanding but omits critical details like pagination limits and the fact that 'all' is constrained by the default limit. This leaves gaps for an agent to fully understand the tool's behavior.

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?

Both parameters (spaceKey and limit) have descriptions in the schema, covering 100% of parameters. The tool description adds no additional parameter semantics beyond the schema, matching the baseline expectation.

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 tool lists pages within a Confluence space, using the specific verb 'Get' and resource 'pages.' It distinguishes itself from siblings like get_page_by_id or get_page_by_title by specifying space-level scope.

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 tool is for retrieving a collection of pages in a specific space, which provides clear context for selection. However, it doesn't explicitly mention when not to use it (e.g., for searching across spaces or finding a single page by title) or name alternatives.

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