Remove a collection and all its documents from Outline wiki to manage content organization.
Delete a collection. All documents in the collection will also be deleted.
| Name | Required | Description | Default |
|---|---|---|---|
| collectionId | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It helpfully reveals the destructive cascading effect ('All documents in the collection will also be deleted'), which is critical context. However, it doesn't mention permissions required, whether deletion is reversible, rate limits, or what happens to the response.
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 (two sentences) with zero wasted words. The first sentence states the core action, and the second sentence provides critical behavioral context. Every sentence earns its place.
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 operation with no annotations and no output schema, the description does the minimum viable job by stating the action and its cascading effect. However, it lacks important context about permissions, reversibility, error conditions, and what the response contains, leaving significant gaps for an AI agent.
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 schema has 0% description coverage for its single parameter, but the description doesn't provide any parameter-specific information. However, with only one parameter (collectionId), the tool's purpose is straightforward enough that the description's clarity about what gets deleted provides adequate context for understanding the parameter's role.
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 action ('Delete') and resource ('a collection'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_document' or 'batch_delete_documents' beyond mentioning that documents in the collection will also be deleted.
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 provides no guidance on when to use this tool versus alternatives like 'delete_document' or 'batch_delete_documents'. It mentions the cascading effect on documents, but doesn't specify prerequisites, exclusions, or appropriate contexts for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.