notion_read_page_markdown

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

No annotations are provided, so the description carries the burden, and it does disclose the performance trait (direct markdown endpoint vs block-by-block), the content of the return (special tags for databases, files, embeds), and the preview status of v2 syntax. It omits permission/auth requirements and any size or truncation limits for large pages, which keeps it short of a 5.

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?

Purpose and performance rationale are front-loaded, the sibling routing comes next, parameter notes last. Every sentence adds information; nothing restates the title or the schema.

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?

An output schema exists so return values need not be explained, and the description covers the format, the alternative tool, and versioning. For a read-only two-parameter tool the remaining gap is minor: nothing about access requirements or behavior on very large pages.

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 0%, so the description must compensate; it does for markdown_version by explaining that "v2" yields the preview Notion-flavored syntax and the default is the stable syntax, which is real meaning beyond the bare enum-less string field. page_id gets only a one-line gloss, leaving the accepted ID format (UUID vs URL) unstated.

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?

States a specific verb and resource (read a page), plus the exact output representation (native Notion-flavored markdown). It explicitly positions itself against the sibling notion_read_page, so an agent can separate them without opening either schema.

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?

Gives an explicit alternative with a condition: use notion_read_page with include_block_ids=True for block-level editing. It also states when to prefer this tool (faster than block-by-block fetching), so both the use case and the exclusion are covered.

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