blender_modifier_remove

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Remove' implies a destructive action, but the description does not state that the modifier is permanently deleted, what happens if the object or modifier does not exist, or whether the operation is undoable. For a mutating operation, this is a meaningful transparency gap.

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?

A single seven-word sentence that is front-loaded with the operative verb. Every word earns its place and there is zero 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?

The tool has no annotations and no output schema, so the description must set expectations for the agent on its own. It fails to mention success/failure behavior, error conditions, permanence of the removal, or any side effects — information an agent needs to safely invoke a destructive operation.

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 description coverage is 100%, so the schema already documents both parameters (object_name, modifier_name). The description adds no additional meaning beyond the schema, but per the baseline for high schema coverage, a 3 is appropriate.

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 states a specific verb ('Remove') and resource ('a modifier from an object'), making the tool's function unambiguous. It is clear and distinct from siblings like blender_modifier_add, blender_modifier_apply, and blender_modifier_configure by virtue of the verb choice, though it does not explicitly call out sibling distinctions.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention relevant workflows such as checking available modifiers via blender_modifier_list first, or choosing between permanent removal versus blender_modifier_apply for baking the effect.

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