notion_list_block_children

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

No behavioral details are provided. The description does not disclose whether the tool is read-only, destructive, or its authentication requirements beyond generic routing. Annotations are absent, so the description fails to fill the gap.

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 short but overly sparse, omitting essential information like input structure and behavior. It front-loads the name but fails to provide value beyond that.

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?

Despite having an output schema, the description is incomplete for a tool that likely requires specifying a block ID. It does not explain input arguments, expected behavior, or error conditions, leaving the agent underinformed.

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 only parameter 'arguments' is described as a 'JSON string of arguments' with no clarification of expected keys (e.g., block_id). Schema description coverage is 0%, and the description adds no meaningful semantics beyond the schema.

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 merely restates the tool name and technical routing details without explaining what listing block children means or what the tool accomplishes. It provides no practical clarity beyond the name itself.

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 on when to use this tool versus alternative Notion tools like notion_get_block or notion_list_comments. The description lacks any context for tool selection.

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