confluence_get_pages_in_space

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the endpoint. It does not mention pagination via the cursor parameter, whether results are flat or hierarchical, supported status values, or any authentication/rate-limit behavior. The GET verb at least signals a read operation.

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 single sentence is compact and front-loads the resource, and the embedded endpoint adds structural value. However, it is under-specified to the point of reading like a title rather than a functional description.

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 5-parameter list endpoint with no annotations and no output schema, the description omits return shape, pagination defaults, and filter semantics. An agent cannot predict the response format or how cursor, limit, and status interact.

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 only 20% (spaceId alone is documented in the schema), and the tool description adds nothing about parameters. The endpoint reference hints at the space ID, but limit, title, cursor, and status remain completely unexplained, and there are no enums to constrain them.

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 is a noun phrase ('Pages in a space') with no explicit verb, so the agent must infer the list operation from the HTTP path. It names the resource and scope, but does not distinguish this from siblings like confluence_get_page_descendants or confluence_search_cql, which also return pages.

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?

No guidance is given on when to use this tool versus alternatives. The description never mentions when to prefer it over confluence_search_cql for filtered searches, confluence_get_page for a single page, or confluence_get_page_descendants for a hierarchy.

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