confluence_get_child_pages

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

No annotations are provided, so the description must fully convey behavioral details. It only states the basic function without mentioning pagination (though schema has cursor/limit), depth of children, error handling, or ordering. The description fails to add significant behavioral context beyond the obvious.

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 sentence, which is concise but too terse. It lacks essential details such as pagination behavior and return format. The structure is simple, but the content is insufficient for effective tool usage.

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?

Given the absence of an output schema and the presence of three parameters including pagination controls, the description is severely incomplete. It does not mention return format, pagination protocol, error handling, or usage constraints. The context from sibling tools is not leveraged to provide contrast.

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 67% (2 of 3 params described). The description adds no parameter-level information. It does not explain the limit and cursor parameters or their relationship, nor does it clarify that page_id is required. The description does not compensate for the missing schema description of the limit parameter.

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 retrieves child pages of a Confluence page, using a specific verb and resource. It distinctively separates from sibling tools like confluence_get_page (single page), confluence_get_page_ancestors (ancestors), and confluence_list_pages_in_space (pages in a 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?

No guidance on when to use this tool versus alternatives such as confluence_get_page_ancestors or confluence_search. There is no mention of prerequisites, limitations, or contextual hints for choosing this tool.

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