notion_append_block_children

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

With no annotations present, the description carries the full burden of behavior disclosure. It does reveal a genuinely non-obvious operational detail — the tool refuses/expects a file-path indirection rather than inline JSON — which prevents a likely failure mode. Beyond that, it discloses nothing about side effects, auth requirements, error behavior, or what gets modified on the parent block.

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 sentences with the high-priority operational warning front-loaded and marked with 'IMPORTANT'. No filler. The only minor waste is that the final clause 'Appends content blocks' is terse to the point of vagueness, though not redundant.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers the single most dangerous operational trap (the file-path indirection), which makes correct invocation achievable. It is nonetheless thin: no return-value expectations, no failure-mode hints, and no statement that block_id must reference an existing block with appendable children.

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 block_id, file_path, and extract are already documented in the schema. The description adds marginal value by clarifying that the file must contain an array of children, but this largely repeats the schema's 'JSON must include a children array' note. Baseline 3 applies.

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 uses a specific verb ("Appends") plus a clear resource ("content blocks"), which distinguishes it from sibling tools like notion_retrieve_block_children (retrieval) and notion_update_block (mutation of existing properties). The target (a parent block) is not stated explicitly, but the tool name and the block_id parameter carry that meaning.

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?

The description delivers a critical invocation requirement — write the JSON payload to a file first and pass file_path — which is essential for successful calls. However, it gives no guidance on when to choose this tool over alternatives such as notion_create_page or notion_update_block, and no exclusions or conditions are stated.

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