blender_manage_modifiers

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It never states that 'apply' bakes the modifier irreversibly into the mesh, that 'remove' destroys the modifier, or that 'add' alters the object's modifier stack. For a 9-parameter mutating tool with zero annotation coverage, these omissions are significant.

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?

Purpose is front-loaded in the first sentence and the rest is a compact bulleted map of parameters. The terse fragment style ('width, segments: for BEVEL') is efficient and every line carries information, though the parameter bullets are grouped in a slightly hard-to-scan way.

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?

An output schema exists so return values need not be described, and the parameter mapping is reasonably covered. But for a 9-parameter mutation tool with no annotations, the description is missing usage selection logic and any disclosure of destructive behavior, leaving gaps for an agent to resolve on its own.

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 0%, so the description must compensate, and it does add real meaning: it maps levels to SUBSURF, width/segments to BEVEL, and target_object/operation to BOOLEAN. However it omits semantic guidance for object_name, modifier_name, and modifier_type beyond examples, so roughly a third of the parameters remain unexplained in both schema and description.

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 first line names a specific resource ('modifiers on an object') and the action values ('add', 'remove', 'apply') clarify the verb class. This distinguishes it from blender_manage_material and blender_modify_object by subject matter, though it never explicitly contrasts with those siblings. Clear enough for an agent to identify the tool's domain.

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 lists the valid 'action' values but gives no guidance on when to use each one, what prerequisites exist (e.g. an existing modifier_name for remove/apply), or how this differs from blender_modify_object. An agent gets the vocabulary but not the decision criteria.

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