get_block_children

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

No annotations are provided, so the description must indicate safety and behavior. It implies a read-only operation via 'list' and 'read', but does not disclose pagination details, rate limits, or the response format. This is adequate for a simple listing but lacks depth.

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 deliver the essential information without any filler or redundancy. 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?

With no output schema and no annotations, the description should clarify return behavior. It states the tool lists direct children but does not mention that the response is an array of block objects or that pagination is supported. This is adequate for a simple read operation but leaves some gaps.

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% with clear parameter descriptions. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 (list), the target (direct children of a block or page), and the intent (read the content of a Notion page). This distinguishes it from siblings like get_block (fetches a single block) and get_page (fetches page metadata).

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?

Provides explicit use-case guidance: 'Use this to read the content of a Notion page.' This implies the tool is for reading page content rather than retrieving block metadata. However, it does not explicitly mention alternatives or when not to use it.

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