Move a page to the trash. For folder pages, the entire subtree is trashed. The landing page cannot be deleted; delete the collective instead.
Trash a page (recoverable from the Collectives page trash). Folder pages take their entire subtree with them. The Landing page cannot be deleted — delete the collective itself instead.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | ||
| collectiveId | Yes |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses the destructive side effect (trash), recoverability, subtree cascade behavior, and the Landing page restriction. Annotations already include destructiveHint true, and the description adds meaningful behavioral details without contradicting them.
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, each adding distinct information: the primary action, the subtree side effect, and the Landing page exception. No redundancy or fluff.
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?
Covers the essential behavior, side effects, and exceptions for a simple mutation. Lacks explicit parameter semantics and return/error behavior, but there is no output schema and the operation is low-complexity.
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 has 0% description coverage and the description adds no meaning beyond the parameter names. collectiveId and pageId are self-explanatory to some degree, but the description does not clarify their relationship, whether pageId is scoped to the collective, or any other parameter-specific requirements.
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?
Description opens with a clear verb and object ('Trash a page'), distinguishes recoverable trash from permanent deletion, and explicitly names the one exception (Landing page), making the tool's purpose unambiguous relative to sibling delete/purge operations.
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?
Provides explicit when-not-to-use guidance: folder pages move their entire subtree, and the Landing page cannot be deleted and should be handled via delete_collective. It does not explicitly contrast with purge_page or restore_page, but 'recoverable' and 'trash' make the primary use case clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.