notion_append_content

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

With no annotations provided, the description carries the full burden. It discloses that markdown is parsed into blocks and appended to the end of the page, and lists supported markdown elements. It doesn't discuss error cases or permissions, but the core behavioral traits are transparent and complete for a simple append operation.

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 well-structured: a one-sentence purpose, a brief explanation of parsing behavior, a list of supported markdown features, and clear parameter definitions. Every sentence provides useful information with no redundancy or filler.

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?

The description covers both required parameters, explains the input format, and describes the append operation. It doesn't address edge cases like empty content or invalid page_id, but the tool is relatively simple and the output schema is present, so the description is sufficiently complete for an agent to use it correctly in most scenarios.

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 schema provides only names and types with no property descriptions (0% coverage). The description fully compensates by explicitly defining page_id as 'the page to append to' and content as 'markdown text to append,' and it elaborates on the content format. This adds substantial meaning 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 clearly states the tool appends markdown content to an existing Notion page, with a specific verb (append), resource (existing page), and scope (end of page). This distinguishes it from siblings like notion_replace_page_content or notion_update_page_content, which replace or update content rather than append.

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 provides clear context for when to use this tool: when you want to add content to the end of an existing page. It doesn't explicitly mention alternatives or exclusions, but the append semantics and 'existing page' phrasing imply the appropriate use case and distinguish from creation or replacement.

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