Add to a Notion page

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

Annotations already declare destructiveHint=false and openWorldHint=true; the description reinforces this with 'Nothing already on the page changes' and adds cost information ('Free') not present in annotations. It does not warn that repeated calls with the same payload will duplicate content (idempotentHint=false), which is a meaningful gap for an 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?

A single front-loaded sentence carries the verb, scope, parameter hints and alternative source, followed by two short clauses on side effects and cost. No filler sentences.

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 mutation tool with no output schema and two undocumented parameters, the description should say what comes back (the appended block, a URL?) and how includeSchedule behaves. It covers the important non-destructive guarantee but leaves the agent guessing on return values and on one of the two content modes.

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 only 50%: pageId and content are documented in the schema, but includeSchedule and swipefileCollection have no schema descriptions. The description names all three content modes, which helps, but it never explains what swipefileCollection expects (an ID? a name?) or what includeSchedule:true actually attaches.

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 (add/append), a resource (existing Notion page), and a precise scope ('to the END'), which separates it from save_to_notion and export_schedule_to_notion in the sibling list. It also names the content modes it accepts, so an agent knows what payload shape fits.

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?

Names list_notion_pages as the source of the pageId, giving the agent the prerequisite step. 'Nothing already on the page changes' implies this is for additive edits to existing pages rather than creation, but it never explicitly says to use save_to_notion instead when creating a new page.

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