Get Page Children

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

The description is consistent with the readOnlyHint annotation (a read operation). It adds minimal context beyond the annotation by specifying that it returns both pages and folders. No additional behavioral details (e.g., pagination behavior, default content inclusion) are disclosed, but given the annotation coverage this is acceptable.

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?

A single, concise sentence conveys the tool's core purpose with no filler. The description is front-loaded and every word contributes to understanding the tool's function.

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 that the output schema exists, annotations are present, and parameter schema is comprehensive, the description is sufficient for a straightforward read-only retrieval tool. It could mention that child folders are included based on include_folders, but this is already captured in the schema. The description provides enough context for basic selection and invocation.

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?

The schema provides 100% coverage for all 7 parameters with descriptions, so the baseline is 3. The tool description adds no parameter-level meaning beyond what the schema already provides, such as clarifying the relationship between include_content and convert_to_markdown, but the schema itself is adequate.

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') and the resource ('child pages and folders of a specific Confluence page'). It differentiates from siblings like 'confluence_get_page' (which retrieves a single page) and 'confluence_get_space_page_tree' (which retrieves the full space tree) by focusing specifically on children of a given 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?

There is no explicit guidance on when to use this tool versus alternatives such as 'confluence_get_space_page_tree' or 'confluence_get_page'. The description does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and sibling list.

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