notion_replace_page_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 explicitly discloses the destructive behavior: 'Overwrites all existing content.' This tells the agent the operation is destructive, though it does not discuss permissions, reversibility, or edge cases like clearing the page with empty markdown.

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 compact and front-loaded with the core action in the first sentence. Supporting details (overwrite warning, read-first advice, alternative tool) are provided in a crisp, scannable structure without excess.

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 tool is a destructive mutation with no annotations, yet the description covers what it does, when to use it, what to do first, and how to avoid unintended edits. Parameter semantics are also covered, and since an output schema exists, return values need not be explained. It is complete for the task.

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 adds per-parameter definitions: 'page_id: the page to replace content on' and 'markdown: new page content in markdown format.' These are clear and add meaning beyond the parameter names, though they could include format constraints or examples.

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 opens with a specific verb and resource: 'Replace a page's entire content with new markdown.' It clearly distinguishes from siblings by explicitly mentioning that targeted edits should use notion_update_page_content instead. The scope ('entire content') is precise.

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?

It provides explicit guidance: 'Use notion_read_page_markdown first to see what's there' and 'For targeted edits, use notion_update_page_content instead.' This explains when to use the tool and names a concrete alternative, which is exemplary.

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