notion_replace_page_markdown

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

No annotations are provided, and the description only includes routing information (JWT, tenant, scope). It does not disclose side effects, authentication requirements, rate limits, or what happens to the page during replacement. The output schema is not described.

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 short but wastes space on routing details that are likely automated. It lacks essential information, making it under-specified rather than concise.

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?

Given the complexity of a mutation tool with no annotations, 0% schema coverage, and an undescribed output schema, the description is severely incomplete. It does not equip the agent to use the tool correctly.

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?

The only parameter 'arguments' is described as a JSON string, which adds minimal meaning. With 0% schema description coverage, the description fails to specify expected keys (e.g., page_id, markdown content) or their formats, leaving the agent to guess.

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 merely restates the tool name ('replace_page_markdown') without specifying what it does. It does not mention the verb or resource (e.g., replacing markdown content of a Notion page), making it a tautology.

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?

No guidance is provided on when to use this tool versus sibling tools like notion_get_page_markdown, notion_update_page_markdown, or notion_create_page. There is no context for appropriate usage scenarios.

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