Delete a Blender collection after confirmation, leaving its objects orphaned. Requires explicit confirm to proceed.
Delete a collection. Objects in it become orphaned. Confirm required.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| confirm | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0+hardened.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the destructiveHint annotation, the description discloses a specific destructive consequence—objects become orphaned—and states that confirmation is required. This is meaningful behavioral context that helps an agent anticipate the side effects of calling the tool.
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, front-loaded sentences: action, consequence, and requirement. Each sentence adds distinct information with no filler 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?
For a two-parameter destructive tool with an output schema and a destructiveHint annotation, this description covers the critical operation, side effect, and safety gate. No essential information is missing for a correct invocation.
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 provides 0% description coverage, so the description carries the burden. It clarifies that confirm is required, overriding the schema's default false, but the required name parameter is only implied by the tool name rather than explained.
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 the operation as 'Delete a collection' with a specific resource and meaningful consequence. It differentiates itself from object/material deletion tools by naming collections and describing orphan behavior, so an agent understands exactly what this tool targets.
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?
Gives no guidance about when to choose this over related alternatives like batch_delete, move_to_collection, set_collection_visibility, or list_collections. The only actionable hint is 'Confirm required,' which addresses how to invoke the action rather than when to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.