notion_read

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

With no annotations, the description carries the burden, and it does deliver the one behavior an agent most needs from a read tool: content comes back as Markdown rather than raw JSON blocks. However it says nothing about permissions, size/pagination limits, or truncation on large pages, and does not explicitly confirm the operation is non-mutating.

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?

A single front-loaded sentence with no filler, and the primary resource is named first. It is efficient but borders on under-specified rather than merely concise.

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 simple two-parameter read tool with no output schema and no annotations, the description covers the core contract (what it reads, what format it returns). It is still missing routing guidance among the many sibling read tools and any behavior for the undocumented block_ids parameter.

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 50%: 'page' is well documented in the schema (URL or id, defaults to the active tab), while 'block_ids' has no schema description and is only gestured at by '(or some blocks)'. The description adds partial meaning over the schema but does not explain that block_ids restricts the read to a subset.

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 ('the page (or some blocks)') plus the output serialization (Markdown). It is clear enough to distinguish from write-side siblings like notion_insert or notion_delete_blocks, but it never contrasts itself with notion_outline, which is the closest competing read tool.

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 parenthetical '(or some blocks)' is the only hint about scoping, and it is ambiguous rather than instructive. There is no statement of when to prefer this over notion_outline or notion_screenshot, no prerequisites, and no exclusions.

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