notion_get_block_children

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Get' weakly implies a read-only operation, but the description says nothing about return format, pagination behavior (despite page_size/start_cursor params), permissions, rate limits, or error conditions. This is far from sufficient for a tool with no annotation coverage.

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 three words and front-loaded, but it is under-specified rather than concise. It omits essential information that would make the tool callable without opening the schema, similar to the LOW calibration example where brevity reflected incompleteness.

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, the description should explain what the tool returns (e.g., a paginated list of child blocks) and how pagination works. It provides none of this. For a read tool with pagination parameters, the description is substantially incomplete.

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%, so the schema fully documents block_id, page_size, and start_cursor. The description adds no param semantics beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Get block children' simply restates the tool name without adding distinguishing detail. It names a verb (get) and resource (block children), but does not differentiate from siblings like notion_get_block or notion_append_block_children. This qualifies as a tautology per the rubric.

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?

There is no guidance on when to use this tool versus alternatives such as notion_get_block, notion_get_page, or notion_query_database. No prerequisites, context, or exclusions are provided. An agent must infer usage entirely from the name.

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