delete

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

With no annotations provided, the description carries the full burden and does well: it discloses the page moves to Trash, can be restored from Notion's UI, and is not permanently deleted. It does not mention output/response details or edge cases like already-archived pages, but the core behavioral trait is clearly exposed.

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?

Three short sentences with no filler. The key action is stated first, and the important caveat about not permanently deleting is given immediately, making the definition efficient and easy to parse.

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 one-parameter, no-output-schema tool, the description covers the essential behavior and reversibility. It does not describe the return value or potential errors, but those are less critical for an archive action whose semantics are already clearly defined.

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 100% and the single 'page' parameter already documents 'Page ID or Notion URL to archive.' The description adds no additional parameter-level semantics, but none are needed given the schema already fully explains the parameter.

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 identifies the action as 'Archive (soft-delete)' applied to a Notion page, which is a specific verb+resource. It also clarifies the non-permanent nature, distinguishing this from what the name 'delete' might imply and from any truly destructive delete operation.

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 intended use is implied: use this when you want to archive or soft-delete a page. However, there is no explicit guidance about when not to use it or which sibling tool to prefer in alternative scenarios, such as permanent deletion or moving pages.

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