Permanently delete saved posts. DESTRUCTIVE and IRREVERSIBLE. First call WITHOUT confirmed=true to see which posts will be deleted, then call again WITH confirmed=true after user explicitly approves.
| Name | Required | Description | Default |
|---|---|---|---|
| post_ids | Yes | Array of post IDs to delete | |
| confirmed | No | Must be true to actually delete. First call without this to preview what will be deleted. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description extends the destructiveHint annotation by explaining that the deletion is irreversible and by detailing the required confirmation workflow. It makes clear what is destroyed (the passed posts) and the safety gate that methods must complete, adding context the annotations alone don't convey.
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 sentences with no filler. The first sentence is a strong, front-loaded warning about the tool's core behavior, and the second provides the essential usage pattern.
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?
Given the destructive nature, two parameters, and no output schema, the description is complete. It covers the destructive effect, the confirmation protocol, and the correct order to invoke the tool, enabling a model to call it accurately without additional documentation.
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 description does not add meaningful parameter information beyond the schema, which already describes the post_ids array and the confirmed flag's 'preview' semantics. Since schema coverage is 100%, the baseline of 3 is appropriate.
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 begins with the specific action 'Permanently delete saved posts,' naming the verb and resource. It also includes a prominent DESTRUCTIVE warning and is easily distinguished from its siblings, which are mostly read or labeling tools.
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?
It gives an explicit invocaction protocol: first call without confirmed=true to preview, then call with confirmed=true only after user approval. This is concrete when-to-use and when-not-to-use direction, leaving no ambiguity about avoiding direct destructive calls.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
