Read Notion document

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

The description adds behavioral detail beyond the annotations by specifying the output format ('Markdown and revisions') and the batch capability ('up to eight'). It also notes that search must be 'unambiguous', giving insight into potential failure conditions.

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 a single, well-structured sentence that front-loads the core purpose ('Resolve and fetch') and packs in key constraints (ID, URL, or search; up to eight pages; output format). There is no wasted text.

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 no output schema and moderate complexity, the description appropriately covers the return type ('Markdown and revisions') and the number of documents. It does not mention handling of missing required parameters, but this is partially implied by the schema. The description is sufficiently complete for a read tool with strong annotations.

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 already describes the 'source' and 'sources' parameters with coverage of 50%. The description adds the nuance that search must be 'unambiguous', which is useful, but it does not explain timeout_ms or max_output_bytes. Overall, the description provides minimal additional parameter semantics.

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 with a specific verb ('Resolve and fetch') and resource ('Notion pages'), and includes the scope of up to eight pages. It also distinguishes itself from the sibling 'notion_publish_document' by focusing on reading, not writing.

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 gives clear context: it is for reading/fetching Notion documents, which is distinct from the sibling publish tool. It does not explicitly mention when to use alternatives, but the tool name and description make the intended use obvious.

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