notion_read_page_markdown

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

With no annotations, the description carries the burden of disclosing behavior. It reveals that the tool 'uses the direct markdown API endpoint', is 'faster than block-by-block fetching', and 'returns Notion's own markdown representation including special tags'. This adds meaningful context about performance and output format, though it doesn't explicitly state read-only safety or error behavior.

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: three sentences cover purpose, implementation benefit, and an explicit alternative. Every sentence adds value, with no redundant or irrelevant content.

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 tool with a single parameter, clear purpose, and an existing output schema, the description is complete. It covers what the tool does, why it's useful, when not to use it (with a named alternative), and the parameter meaning. There are no significant gaps.

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 schema has 0% description coverage, so the description must compensate. It adds 'page_id: Notion page ID,' which is minimal and essentially repeats the schema title 'Page Id'. This provides only basic meaning and no additional format or context details, so the compensation is weak.

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 clearly states the tool's function: reading a Notion page's content as markdown. It distinguishes itself from sibling tools, particularly notion_read_page, by explicitly naming the alternative for block-level editing, making the purpose unambiguous.

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 provides explicit when-to-use guidance by saying 'For block-level editing (update/delete individual blocks), use notion_read_page with include_block_ids=True instead.' This names the alternative and gives a clear exclusion, along with a performance rationale for using this tool.

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