API-get-block-children

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

No annotations are provided, so the description carries the full burden. It states 'Retrieve' implying a read-only operation, but lacks details on permissions, rate limits, error handling, or what 'block children' entails (e.g., nested content). The description is minimal and doesn't disclose behavioral traits beyond the basic action.

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 ('Notion | Retrieve block children') with no wasted words. It front-loads the key information (context and action) efficiently, though it may be overly brief for a tool with three parameters and no annotations.

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 tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return values (e.g., list of child blocks), pagination behavior, or error cases. For a retrieval tool with moderate complexity, more context is needed to guide effective use.

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 description coverage is 100%, with clear documentation for block_id, page_size, and start_cursor. The description adds no additional parameter semantics beyond what the schema provides, such as examples or context for 'block children'. This meets the baseline 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 resource ('block children') with the Notion context. It distinguishes this as a read operation (vs. create/update/delete siblings like API-create-a-database or API-delete-a-block), though it doesn't explicitly differentiate from similar retrieval tools like API-retrieve-a-block or API-retrieve-a-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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention when to retrieve block children versus retrieving a block directly (API-retrieve-a-block) or searching (API-post-search), nor does it specify prerequisites like needing a valid block_id or handling pagination.

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