Append Block Children

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

Annotations indicate this is a write operation (readOnlyHint=false). The description adds that it requires insert capabilities, but does not disclose detailed behavioral traits such as what happens if the parent block is deleted, rate limits, or idempotency. It does mention the optional position object for insertion points, adding some context.

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 with only two sentences, no wasted words. It is front-loaded with the purpose and includes a key usage tip about the position parameter.

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 complexity of the input schema (nested block structures, many block types) and no output schema, the description is too minimal. It does not summarize common use cases, limitations, or what the return value looks like. It relies entirely on the schema for details.

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%, so baseline is 3. The description adds value by explaining the 'position' object usage ('insert at the start, end, or after a specific block'), which is not obvious from the schema alone. However, it does not elaborate on the complex children schema, which is already detailed in 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 clearly states the verb 'append' and resources 'new children blocks' to a 'specified parent block'. It is specific but does not differentiate from siblings like notion_append_content or notion_append_markdown, which could be used for similar purposes.

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 mentions 'requires insert content capabilities' which is a usage prerequisite, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it state 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.