notion_update_page_markdown

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

Annotations already mark this as destructive (destructiveHint=true) and non-read-only, so the description's job is to add context about what gets destroyed; instead it never warns that page content may be overwritten or lost. It does add some value by explaining the governed routing and the write-approval flow ('approval_ref: Approved platform task UUID when resuming a write'), but it also lets the agent 'claim' a read or write effect even though annotations establish this is genuinely a write/destructive operation. This leaves the destructive implications critically undisclosed.

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 well-organized, using a clear header plus a bullet-style Args list with one line per parameter. The routing sentence and parameter block are each reasonably concise. However, the opening sentence is a tautology that wastes the prime position where substantive purpose information should be.

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 destructive, idempotent write operation with 7 parameters and zero schema descriptions, this is materially incomplete. It omits what the operation actually does to a page, what the arguments payload must contain, how it differs from notion_replace_page_markdown, and what the destructive consequences are. The output schema reduces the need to document return values, but the operational semantics an agent needs to call this correctly are absent.

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?

With 0% schema description coverage, the description carries the full burden for parameter meaning, and it does provide one-line glosses for all seven envelope parameters. However, the core payload parameter, `arguments`, is described only as 'JSON string of arguments for the connector operation' — a black box. An agent cannot construct a valid arguments JSON (what identifies the page, what markdown content, which properties) from this description, which is the single most important parameter for actually invoking the update.

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 'Notion connector operation `update_page_markdown`', which merely restates the tool name rather than explaining what the operation semantically does. The only additional sentence concerns routing through 'governed connector authority', which is an operational constraint, not a purpose. An agent cannot tell from the description what updating page markdown entails or how it differs from the sibling notion_replace_page_markdown.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention the near-identical sibling notion_replace_page_markdown, the more general notion_update_page, or notion_get_page_markdown, so an agent has no basis for choosing among them. No usage context, prerequisites, or exclusion criteria are provided.

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