Move Page to Trash

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds valuable context beyond annotations: that the action is reversible via notion_undo or Notion's trash. It doesn't cover permissions or rate limits, but the reversibility note is meaningful added value.

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?

Two concise sentences, front-loaded with the core action and followed by the reversibility note. Every word earns its place with no redundancy.

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 single-parameter mutation tool with rich annotations, the description covers the essential action and reversibility. It doesn't explain permissions or potential side effects (e.g., what happens to child blocks), which would be helpful, but it's largely complete for the scope.

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 must compensate. It mentions 'page' as the target but doesn't clarify that the parameter is a page ID string. Since there's only one parameter and its name is self-explanatory, baseline 3 is appropriate given the low schema coverage.

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 a specific verb ('Move') and resource ('page or database row') with a clear destination ('the Notion trash'). This distinguishes it from siblings like notion_delete_blocks and notion_update_page by identifying exactly what operation occurs.

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 (when you want to trash a page), but doesn't explicitly compare to alternatives like notion_delete_blocks or notion_update_page. It mentions recovery via notion_undo, which is helpful, but doesn't state when to prefer trash over other deletion methods.

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