notion_pages

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

With no annotations, the description carries the full burden and discloses almost nothing: it does not say that archive/restore are mutations, that archive is reversible via restore, what permissions or parent-page defaults apply, or that search results are paginated (page_size 1-100, start_cursor). Only the bare action names hint at 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?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification for a five-way multiplexed tool.

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?

No output schema and no annotations mean the description should explain return shape, pagination and destructive semantics, and it does none of these. For a complex action-union tool the rich schema compensates substantially, but an agent reading only the description would not know that archive is destructive-but-reversible or how to page through search results.

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 effectively 100% — the single 'payload' parameter is a fully documented discriminated union with per-action descriptions. The description adds no parameter meaning of its own, so the baseline 3 for high schema coverage 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 the resource (Notion pages) and enumerates the five operations (create, archive, restore, search, update), which is enough to distinguish it from siblings notion_blocks, notion_database, notion_comments and notion_users. It is clear at the level of 'page operations' but does not describe what any individual operation does, leaving that to the 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?

There is no guidance on when to use this tool versus the sibling database/block tools, nor on how to pick among the five actions. The parenthetical action list merely names alternatives rather than stating selection conditions; the actual 'use this action to…' guidance lives in the schema, not the description.

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