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

Annotations already declare this is a non-read-only, open-world, non-idempotent write. The description adds useful context beyond annotations: it describes the page contents (live-flow link, summary, questions to confirm, Mermaid diagram) and explains the connection-error behavior. It does not cover permissions or rate limits, but it is notably more informative than the annotations alone.

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?

Three sentences, front-loaded with the core action, then the page contents, then the error behavior. Every sentence earns its place and there is no repetition or filler.

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 write tool with annotations covering safety and no output schema, the description is nearly complete: it explains what is created and how connection failures surface. It could go slightly further by noting permissions or whether repeated calls create duplicate pages, but the core operational picture is clear.

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 100%, so all four parameters are already documented in the input schema. The description adds no additional format, default, or constraint information beyond what the schema provides, which fits the baseline of 3 when the schema carries the full parameter burden.

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 a specific verb ('Save') and resource ('a flow as a new Notion page under a parent page'), and the Notion-specific wording distinguishes it from sibling tools like send_flow_to_confluence or send_flow_to_jira. It also specifies what the resulting page contains, which removes ambiguity about the tool's effect.

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?

The description does not say when to use this tool versus alternatives such as export_flow, save_flow_to_drive, or the other send_flow_to_* tools. It implies usage through the purpose statement, but provides no explicit when/when-not guidance or prerequisites like needing a parent page ID from find_notion_pages.

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