notion_append_block_children

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only mentions routing and a generic 'arguments' parameter. It does not disclose what the operation does (e.g., appends children, requires block ID), any side effects, or permissions needed.

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 wastes space on routing details ('Routes through /api/tools/invoke under your JWT...') that are irrelevant for an agent. It fails to include essential information about the tool's purpose and parameters.

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 (inferred from context), the description does not hint at the return value or behavior. The combination of no annotations, vague parameter docs, and lack of usage context makes it incomplete for an agent to use correctly.

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 0%, so the description must explain the parameter meaning. It only says 'JSON string of arguments for the connector operation', which adds no value beyond the schema. The required fields within that JSON (e.g., block_id, children) are not documented.

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 repeats the tool name and mentions it's a Notion connector operation, but does not explicitly state that it appends child blocks to a parent block. It lacks a clear verb+resource statement, making it ambiguous.

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 is provided on when to use this tool versus other Notion tools (e.g., notion_create_page, notion_update_block, notion_delete_block). An agent would have to infer usage from the name alone, which is insufficient.

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