notion_retrieve_block_children

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

With no annotations, the description must fully communicate behavioral traits. It only states 'retrieve' (implying read-only) but does not disclose pagination behavior, rate limits, or whether it returns multiple pages. The schema shows pagination parameters, but the description does not mention them, leaving agents to infer behavior from schema alone.

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 extremely concise at one sentence, with no redundant information. It front-loads the core action. While brevity is valued, it could benefit from a brief note on pagination or typical use cases without becoming wordy.

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 the complexity (4 parameters, no output schema, no annotations), the description is incomplete. It does not describe the return format structure (e.g., a list of block objects) or pagination behavior beyond what is hinted in the schema. For a tool used to retrieve nested content, more context is needed.

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 input schema has 100% description coverage, including detailed guidance for each parameter (e.g., format parameter explains when to use 'json' vs 'markdown'). The tool description adds no additional parameter semantics, so it does not exceed the baseline of 3 for high schema coverage.

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 ('retrieve') and the resource ('children of a block'), which distinguishes it from sibling tools like 'notion_retrieve_block' (single block) and 'notion_append_block_children' (modifying children). However, it does not elaborate on what 'children' means in Notion (child blocks), which could add slight ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this tool is intended for retrieving hierarchical content, while 'notion_retrieve_block' is for a block's own properties. The description lacks context for preference.

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