notion_retrieve_block_children

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that the operation is a read ('Retrieves') and that pagination is supported, which is useful. It does not mention response format, error behavior, or rate limits, but for a simple read operation the disclosed traits are reasonable.

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 wasted words. The core action is front-loaded, the parenthetical makes the content type concrete, and the pagination note is a valuable addition. It neither repeats the tool name nor pads with filler.

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?

The schema is rich enough to cover all parameter semantics, and the description states the core operation and pagination support. However, with no output schema and no annotations, the description does not explain what the response looks like beyond the extract parameter's schema description. It is functional but slightly minimal for a tool with four parameters.

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 has 100% coverage with descriptive entries for all four parameters, including the extract behavior and pagination cursors. The description adds no parameter-specific information beyond the schema, so the baseline of 3 applies.

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 states a specific verb 'Retrieves', a specific resource 'children blocks', and gives concrete exmples (paragraphs, headings, lists). The phrase 'of page or block' also signals that both container types are valid inputs. This clearly distinguishes it from sibling tools like notion_retrieve_block, which would fetch a single block rather than its children.

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 clearly implies usage: call this when you need the child blocks of a page or block. However, it does not explicitly mention when not to use it or point to any alternative tool, such as using notion_retrieve_block for the block itself. The context is clear, but the routing guidance is left implicit rather than stated.

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