confluence_get_page_children

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

The description discloses the behavioral constraint that v2 returns only child summaries and that specific fields (content, version, etc.) are not populated. No annotations are provided, so the description fully covers the read-only nature and limitations.

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 efficiently convey purpose, key constraint, and actionable guidance. No redundant or extraneous 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 simple tool with two parameters and no output schema, the description adequately communicates the return behavior and limitations. It could mention pagination or the structure of summaries, but the depth is reasonable.

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%, and the schema already clearly defines both parameters (pageId and limit). The description does not add significant new meaning beyond stating 'child pages' context, which is already inferred from the tool name.

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 it retrieves child pages of a Confluence page, specifying that v2 returns only summaries and listing which fields are not populated. This distinguishes it from sibling tools like confluence_get_page.

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?

It indicates when to use this tool (to get child pages) and advises fetching each child by id with confluence_get_page for full details. However, it does not explicitly state when not to use it or mention alternative tools for related tasks.

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