notion_update_page_content

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

With no annotations provided, the description must disclose behavior itself. It explains the search-and-replace operation and the delete-via-empty-string behavior, but does not specify whether all occurrences or only the first are replaced, case sensitivity, or the behavior when old_text is not found. This ambiguity for a mutation tool is a gap.

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 concise and well-structured: a clear one-line summary, a brief usage workflow, and a compact parameter list. No wasted words.

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 has a simple signature and an output schema, so return values need no explanation. The description covers the core behavior and usage flow, but omits edge cases like multiple occurrences or not-found handling, leaving some ambiguity for a production editing tool.

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 meaningful semantics for all three parameters: page_id identifies the page, old_text must be exact, and new_text can be empty to delete. This compensates well for the bare schema, though format details are not provided.

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 states the verb 'Edit' with resource 'page content' and the specific method 'search-and-replace', clearly distinguishing it from sibling tools like notion_replace_page_content and notion_append_content. It also explicitly explains the find-replace mechanism.

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 instructs users to first use notion_read_page_markdown to view current content and copy exact text, which is a clear usage prerequisite. It does not explicitly exclude alternatives or state when not to use, but the context is clear enough for a targeted edit.

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