Delete a specific Blender object by name without altering unrelated scene elements.
Delete exactly one existing Blender object by name. Does not clear unrelated scene objects.
| Name | Required | Description | Default |
|---|---|---|---|
| target_name | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, and the description aligns by stating 'Delete'. It adds the nuance that only the named object is affected and unrelated objects are untouched, which is additional context beyond the annotation. However, it doesn't disclose failure modes or reversibility, so it only partially adds value.
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, minimal waste, the core action is front-loaded. The clarifying note is useful and not redundant.
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 simple one-parameter delete tool with destructive annotations, the description provides essential scope and target information. It doesn't cover error handling or return values, but given the simplicity and annotation coverage, it's largely sufficient.
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 0%, so the description must clarify the parameter. It does so by specifying the object is identified by name and that it must be an existing object. This adds meaning beyond the bare string schema, though it doesn't detail exact matching rules.
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 (delete) and resource (Blender object) with scope qualifiers (exactly one, by name). The second sentence clarifies it doesn't clear unrelated objects, distinguishing it from broader scene-clearing operations.
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 clearly indicates the tool's purpose for single-object deletion, but it doesn't explicitly contrast it with alternatives like blender_delete_snapshot or provide when-not-to-use conditions. It has clear context but lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.