notion_archive_page

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

The description explains the archive boolean behavior and notes the pageId format. Annotations already provide destructiveHint and idempotentHint; the description adds context on the toggle semantics.

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?

Single sentence with parenthetical explanation of parameter values. No extraneous words, front-loaded with action and key detail.

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 toggle with 2 parameters and annotations covering destructive/idempotent hints, the description suffices. No output schema exists, but return values are not critical for an action tool. Could mention success/failure behavior but not required.

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 100%. The description clarifies the archive parameter's meaning (archive vs. unarchive) beyond the schema's default and boolean type. pageId is well-described in schema; description adds minimal but acceptable value.

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 archives or unarchives a Notion page, with explicit parameter mapping. It distinguishes from sibling tools like notion_update_page by focusing solely on archive state.

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 implies usage for toggling archive state but provides no guidance on when not to use it or alternatives like notion_update_page or notion_get_page for other operations.

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