notion_append_content

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

With no annotations, the description carries the burden well: it discloses that markdown is parsed into blocks, enumerates the supported markdown constructs, and notes that 'silent' suppresses the notifications this write would otherwise send. It does not cover permission requirements or size limits, but the core behavior of this mutation is well surfaced.

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?

Front-loaded with a one-line purpose, followed by a compact parsing note, a supported-syntax list, and per-parameter notes. The markdown feature list is slightly long but each item prevents a real ambiguity, so little is wasted.

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?

An output schema exists, so return values need not be described, and all four parameters are explained. What remains missing is permission/auth requirements and any content-size or error behavior for this write tool with zero annotation coverage.

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 0%, so the description must compensate and it does: page_id explains it can be any block supporting children, content is markdown text, position enumerates 'end'/'start'/block ID plus how to obtain block IDs via notion_read_page(include_block_ids=True), and silent is explained. Every parameter gains meaning beyond the bare 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?

States a specific verb and resource ('Add markdown content to an existing Notion page') and clarifies scope ('existing'). However, it does nothing to distinguish itself from near-identical siblings such as notion_insert_page_content, notion_replace_page_content, and notion_update_page_content, which an agent must choose between.

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?

Implied usage is clear from 'existing page' (not for creating pages) and the position parameter describes insertion modes, but there is no explicit when-to-use guidance and no mention of when to prefer insert/replace/update siblings instead.

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