notion_restore_page

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the action but does not disclose what happens if the page is not archived, whether permissions are required, what the response contains, or whether the operation is reversible. This is a minimal description for a mutation tool.

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 two short, direct sentences with the action front-loaded and a single parameter clarification. Every word earns its place; there is no redundancy or 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?

The tool is simple with one parameter and an output schema, so the description covers the basic purpose and parameter adequately. However, the lack of behavioral caveats (e.g., error conditions, prerequisites, or effects on page state) leaves some gaps, especially given there are no annotations to supplement it.

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?

With schema description coverage at 0%, the description compensates by explaining that 'page_id' is 'the archived page to restore,' adding meaning beyond the schema's generic 'Page Id' title. While it does not specify a format or additional constraints, the single parameter is clearly interpreted.

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 uses a specific verb ('Restore') and a clear resource ('an archived page from the Notion trash'), which directly distinguishes it from sibling tools like notion_archive_page. The purpose is immediately obvious and 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 clear context that this tool is for restoring pages that are in the Notion trash, but it does not explicitly mention when not to use it or point to alternatives such as notion_archive_page for the inverse operation. No exclusions or alternative tool references are given.

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