Delete multiple Blender objects in a single operation by specifying object names or identifiers, simplifying cleanup and reducing repetitive deletion steps.
批量删除。
| Name | Required | Description | Default |
|---|---|---|---|
| objects | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations or description disclose side effects, irreversibility, or whether undo is supported. Batch delete is inherently destructive, but this is not communicated, making the tool behavior opaque.
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, consisting of only two characters, but it lacks any structured explanation. It is a bare phrase without context or elaboration, which is insufficient for effective use.
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 tool is incomplete in context: it does not describe return values, error handling, or the meaning of the 'objects' parameter. While sibling tools hint at batch operations, the description alone does not provide enough information for an agent to use it correctly.
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 'objects' parameter is a union of array, object, and string, but the description provides no explanation of what values should be passed or how they are interpreted. This ambiguity is critical for a delete operation.
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 'Batch delete' clearly indicates a verb ('delete') and a resource ('batch'), but does not specify what is being deleted. In the context of sibling batch tools, it likely refers to objects, but the description alone lacks that specificity.
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?
No guidance is provided on when to use this tool versus alternatives like delete_object or other batch operations. There is no mention of scenarios or prerequisites, leaving the agent without clear direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.