Get Page Descendants

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

Annotations (readOnlyHint=true, destructiveHint=false) already establish this as a safe read operation, lowering the bar. The description adds the behavioral fact that it returns 'all descendants' rather than just direct children, but it does not disclose pagination behavior, ordering, or whether the traversal is recursive. This provides modest additional context beyond annotations.

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 compact docstring with a clear one-sentence purpose followed by a parameter list. It is concise and front-loaded, with no wasted words, though the argument descriptions are minimal.

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?

This is a paginated list tool with no output schema. The description fails to explain what the response looks like, how pagination works (e.g., using the cursor), or what constitutes a descendant (recursive vs. direct). For a list operation, this leaves the agent without essential integration information.

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 0%, so the description must compensate. It provides terse but useful meanings: page_id ('Page ID'), limit ('Max results'), and cursor ('Pagination cursor'). These add clarity over the bare schema titles but omit details such as default values, maximum limits, or cursor format.

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 the specific verb 'Get' and identifies the resource as 'descendants of a page' with the qualifier 'all', clearly distinguishing it from sibling tools like get_page_children and get_page_direct_children. The title aligns perfectly with the description.

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 does not explicitly state when to use this tool versus alternatives. The word 'all' implies a broader scope, but there is no direct guidance such as 'use this for all generations, not just direct children' or mention of alternatives. Context is clear but not fully developed.

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