notion_archive_page

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

Annotations already declare this as destructive, non-read-only, and idempotent. The description adds useful operational context: the operation routes only through the governed connector authority, and writes require an approval_ref when resuming. It does not, however, disclose what archiving affects or whether it is reversible, so it adds only partial behavioral value beyond the annotations.

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 compact and well organized, with a short intro followed by a clear list of all parameters. Each parameter line carries some useful semantic information. The main inefficiency is the redundant first sentence, but overall the structure is efficient and scannable.

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 destructive connector operation with seven optional parameters, an opaque 'arguments' JSON payload, and no differentiation from sibling Notion tools, the description is incomplete. An agent would not know what to place inside 'arguments', what the archive effect is, or when this should be used over related operations. The output schema exists, but it does not compensate for missing invocation semantics.

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 0%, so the description is the only source of parameter meaning. It gives one-line definitions for all seven parameters, which helps clarify idempotency_key, effect, approval_ref, and routing-related fields. However, the central 'arguments' parameter is left as a generic 'JSON string of arguments for the connector operation' with no detail about the expected Notion archive_page payload, such as page_id or archived flags.

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 opens with 'Notion connector operation `archive_page`', which simply restates the tool name and adds the platform tool identifier. It never explains what archiving a page actually does, such as removing it from active views or moving it to trash, and it does not differentiate this operation from related siblings like notion_trash_page or notion_delete_block.

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 alternatives, and no mention of prerequisites or exclusions. The only contextual note, routing through the governed project/account connector authority, is an invocation constraint rather than a selection criterion. With many similar Notion sibling tools, the absence of routing guidance is a significant gap.

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