list_child_pages

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond those annotations: it lists only direct children (not descendants) and preserves sidebar order. It also explains the space-root behavior, which is a non-obvious call pattern.

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 short sentences with zero filler. The core purpose is front-loaded, and the conditional usage guidance is placed immediately after. Every word earns its place.

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 read-only list operation, the description captures the essential behavior, ordering, and the special root-page case. Pagination is covered by the schema's cursor and limit descriptions. No output schema exists, so an agent might not know the exact return shape, but the tool's purpose is simple enough that this is a minor gap rather than a critical omission.

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%, so limit and cursor are already documented. The description adds value by clarifying the relationship between page_id and space_id, specifically that space_id is used for root pages while page_id is omitted. This is a semantic decision rule not present in the schema.

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 verb ('List'), the specific resource ('direct child pages of a page'), and an important behavioral detail ('in sidebar order'). This distinguishes it from broader tools like list_pages and get_page without needing to open the schema.

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 gives explicit guidance for the space-root case: 'Omit page_id and pass space_id for space-root pages.' This is a clear contextual usage rule. It does not explicitly name alternatives or say when not to use the tool, but the direct-child scope makes the intended use reasonably clear.

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