blender_object_delete

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

With no annotations, the description alone must convey behavioral implications. It only states the deletion action but does not mention side effects like irreversibility, impact on related objects (e.g., children), or error handling if the name doesn't exist. This lack of detail leaves the agent unaware of potential consequences.

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 a single, concise sentence that front-loads the primary action. It contains no redundant words and is appropriately sized for its function. Structure is direct and clear.

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 simple schema, the description might seem sufficient, but it omits key context: what happens on success or failure, whether a confirmation is needed, or any side effects on the scene. For a destructive operation, this lack of completeness could lead to misuse. The absence of an output schema further compounds the ambiguity.

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 already defines the parameter 'name' with a description 'Name of the object to delete'. The tool description merely repeats 'by name' without adding extra context, such as expected format, case sensitivity, or uniqueness. It does not enhance the schema's meaning.

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 action: 'Delete an object by name'. It specifies the verb 'delete' and the resource 'object', distinguishing it from other object operations like create, list, or transform. The scope is unambiguous.

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 provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention conditions like object existence, or whether it should be used before cleanup operations. The user must infer usage from the sibling tools.

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