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

Annotations only cover the read-only safety profile; the description adds the traits that actually affect how an agent behaves: depth/size capping, truncation signalled by `truncated: true`, plain-text flattening of block types, and the Notion-side sharing prerequisite that otherwise causes confusing failures.

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, no filler: output format first, then the truncation caveat, then the prerequisites. Front-loaded and every sentence carries information an agent needs.

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?

There is no output schema, and the description compensates by describing the return shape (plain text block content) and the truncation flag. Combined with the sharing prerequisite and account guidance, nothing essential for a correct call is missing.

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 both parameters are already documented in the schema, including where page_id comes from and when account is required. The description repeats the multi-workspace condition but adds no format or syntax beyond it, so the baseline 3 applies.

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 (read) and resource (one Notion page), plus the exact rendering (plain text covering paragraphs, headings, lists, to-dos, quotes) and the traversal model (block tree walking). This clearly separates it from search_notion_pages, which finds pages rather than reading their content.

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 two concrete conditions: the page must already be shared with the integration, and `account` is passed when multiple Notion workspaces are connected. It stops short of an explicit routing statement such as 'use search_notion_pages first to obtain the page_id', which the schema carries instead.

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