Permanently delete a trashed page from a collective. Requires the page to be in trash first, as this action cannot be undone.
Permanently delete a trashed page. THIS IS IRREVERSIBLE — the page content cannot be recovered after this call. The page must already be in the trash (use delete_page first).
| 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?
While annotations already indicate destructiveHint=true, the description adds crucial context about irreversibility and the precondition of being trashed. This goes beyond the annotations and fully informs the agent of the consequences.
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 extremely concise, using a single sentence plus a warning. Every word adds value, with no fluff or 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?
The description covers the essential context: what it does, the irreversibility, and the prerequisite. It lacks parameter details but for a simple two-integer operation, this is not a significant gap. No output schema is present, so no return value clarification is needed.
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?
The input schema has no descriptions and the tool description does not explain the parameters (collectiveId, pageId). With 0% schema description coverage, the description fails to compensate by clarifying parameter meaning or expected values.
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 verb 'permanently delete' and the specific resource 'trashed page'. It distinguishes from siblings like delete_page (which moves to trash) and restore_page, making the purpose unambiguous.
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 explicitly states the prerequisite: the page must already be in the trash, and instructs to use delete_page first. This clearly tells when to use this tool and differentiates it from alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.