Append To Notion Page

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

The description adds value beyond annotations by explicitly stating 'without replacing or deleting content' and noting 'Risk: safe_write'. This provides context that complements the destructiveHint=false annotation. It does not disclose behavior on missing page IDs or rate limits, but the key behavioral traits are covered.

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: one sentence plus a two-word phrase. Every word serves a purpose, and key information is front-loaded. No unnecessary content.

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 simple append tool with no output schema, the description provides the essential action and safety hint. However, it lacks information about error handling, prerequisites (e.g., page existence), or return values, leaving some gaps for complete agent understanding.

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%, but the description only mentions 'content' generically and does not explain the purpose or format of pageId, content, or requestingAgent. No additional parameter semantics are provided, failing to compensate for the lack of schema descriptions.

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 the resource 'content to an existing Notion page', distinguishing it from sibling tools like notion_create_page and notion_get_page. It explicitly notes that content is added without replacing or deleting, which clarifies its unique function.

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 implies usage for appending content to an existing page, and mentions 'safe_write' as a risk indicator. However, it does not explicitly state when not to use it or compare to alternatives like notion_create_page, leaving some ambiguity for the agent.

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