delete_assetSoft-delete an asset. This is reversible from the Playbook trash for a limited time.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Asset token | |
| organization | No | Workspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one. |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesAdded value: +falseInput schema / properties / contextRemoved value: -{
- "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "token",
- "context"
-]New value: +[
+ "token"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations supply destructiveHint=true and idempotentHint=false, and the description adds genuinely new behavior: the deletion is soft and recoverable from the Playbook trash for a limited time. That materially changes an agent's risk calculus. It stops short of a 5 because it says nothing about permissions or what happens once the trash window lapses.
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 short sentences, no filler, and the critical reversibility caveat is stated immediately after the action. 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 two-parameter, fully documented delete operation with strong annotations, the description covers the essentials an agent needs. Nothing about return values is required since no output schema exists, though a note on the recovery window duration would make it complete.
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 coverage is 100%, with both token and organization fully documented in the schema (including when to omit the workspace slug). The description adds no parameter meaning of its own, so the baseline 3 applies.
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 (soft-delete) and resource (asset), and the 'soft' qualifier meaningfully distinguishes it from a hard destroy or from revert_asset. It does not explicitly name a sibling, so it stops short of a 5.
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?
Implies usage through 'soft-delete an asset' and notes the reversibility window, which hints at when it is safe to call, but it never states when to prefer this over alternatives such as revert_asset, or any prerequisite conditions. Guidance is implied rather than explicit.
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.