append_to_page

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

With no annotations, the description carries the full burden and does well: it discloses that existing content is never modified/removed, that content is appended to the end, and that empty/whitespace-only markdown is rejected before contacting Notion. This goes well beyond the bare schema, though it does not cover permissions, failure modes, or rate limits.

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?

Every sentence earns its place. The main behavior and return shape are front-loaded, followed by compact parameter definitions and a validation note. No repetition 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?

For a two-parameter tool with no output schema and no annotations, the description covers the essential context: what the tool does, what it returns, what each parameter means, and a key edge-case behavior. Nothing critical is missing for an agent to invoke it 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 fully compensate. It does: ref is defined as an alias, notion.so URL, id, or exact page title, and markdown is defined as the same supported subset as create_page with explicit validation behavior. This is exactly the semantic detail the schema lacks.

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 names a specific action (append) and resource (page), states the return shape {appended, url}, and explicitly distinguishes its non-destructive nature from other page operations. This is unambiguous and differentiates it from siblings like create_page and update_row.

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 behavior clearly implies this is for adding content to an existing page rather than creating or updating, and references create_page for markdown semantics. However, it does not explicitly state when to choose this tool over a sibling or mention exclusion conditions.

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