replace_content

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

With no annotations, the description fully discloses atomicity, block ID preservation for matched blocks, dropping of certain element types, and warning behavior for bookmarks/embeds. No contradictions.

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?

Front-loaded with purpose and atomicity. While lengthy, each sentence adds value covering edge cases and exceptions. Could be slightly more concise by referring to docs, but well-structured overall.

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?

Covers return warnings and mentions docs for full details. Lacks explicit output structure but given complexity, it's fairly complete with workarounds for unsupported types.

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 100%, so baseline is 3. The description adds no new semantic details beyond what the schema already provides for page_id, markdown, and dry_run.

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?

Clearly states it replaces all page content with markdown atomically. Differentiates from siblings like append_content and find_replace by specifying it's a full replacement.

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?

Explicitly explains when to use (atomic replacement with ID preservation) and when not to (if source has child_page, child_database, etc., recommending duplicate_page or Notion UI). Provides clear alternatives and contexts.

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