blender_delete_object

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructive and idempotent behavior, and the description reinforces this with "DESTRUCTIVE: permanently removes the object" and adds a specific detail not in annotations: deleting a missing object "returns success with a note." It also discloses the return format (JSON confirming deletion).

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 concise and well-structured, using brief headings (DESTRUCTIVE, Args, Returns, Example). Every sentence adds value, with no redundancy or filler.

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 tool's simplicity and the presence of annotations, the description covers the essential aspects: purpose, input structure, safety, idempotent behavior, return type, and an example. It lacks only minor details like permissions or scene-specific side effects, which are unlikely to be needed for this one-parameter tool.

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?

With schema description coverage at 0%, the description compensates by identifying the `params` input as a DeleteObjectInput containing an exact `name`, and the example clarifies usage (name="Cube"). While it doesn't mention case-sensitivity or the required flag, the schema already contains those details, and the example provides a concrete template.

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 clearly states the exact action: "Delete an object from the scene by name." This specifies the verb (delete), the resource (object), and the method (by name), and it is distinct from sibling tools such as blender_create_primitive or blender_transform_object.

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 establishes a clear usage context: use this tool when you need to remove an object by its exact name. It gives an example and notes idempotent behavior, but does not explicitly contrast with alternatives or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.