confluence_get_page_descendants

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explicitly mentions pagination, default output trimming, and the ability to get raw response via 'full=true'. It does not mention being read-only or any side effects, but the given information is sufficient for basic understanding.

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?

Three sentences, no wasted words. The most important information (purpose and key behaviors) is front-loaded. Every sentence adds unique value.

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 no output schema and a tool that returns a list of pages, the description could mention common fields in the response (e.g., page details) or error conditions. The current description focuses on trimming and pagination but leaves the exact return structure implicit.

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?

Although the input schema already describes all 4 parameters, the description adds context: explaining that output is trimmed by default and that 'full=true' bypasses that, and that the cursor is used for pagination. This extra information enhances understanding beyond the schema descriptions.

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 uses a specific verb ('Get') and resource ('descendants'), and immediately clarifies it includes child pages, grandchildren, etc. This clearly distinguishes it from sibling tools like 'get_page_children' (direct children) and 'get_page' (single 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?

The description explains pagination (using cursor) and the trimming behavior with the 'full' parameter, giving practical guidance on how to use the tool. However, it does not explicitly state when to prefer this over alternative tools like 'get_page_children' for direct descendants, though the purpose implies it.

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