blender_manage_modifier

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

Annotations already indicate destructiveHint=true. The description adds value by specifying which actions ('apply' and 'remove') are destructive, going beyond the annotation. No contradiction. However, it omits other behavioral aspects like output or progression, so 4 is appropriate.

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?

Three sentences, each purposeful: action list with destructiveness note, then usage guidelines. No fluff, front-loaded with core purpose. Exemplary conciseness.

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 5-parameter tool with nested object and no output schema, the description covers actions, destructive behavior, and usage boundaries. Minor gaps: no mention of result/return, or what happens on invalid settings. Still quite complete given the schema richness.

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 100% with parameter descriptions. The description merely lists actions already in the enum without adding deeper meaning (e.g., what 'configure' does vs 'add'). Thus it does not elevate beyond the baseline of 3.

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 actions (add, configure, apply, remove, reorder) on modifiers of an object, using specific verbs and resource. It distinguishes itself from the sibling tool blender_get_object_data by explicitly saying 'Do NOT use for: reading modifier details (use blender_get_object_data with include=['modifiers']).'

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 explicit when-to-use ('need to work with modifiers') and when-not-to-use (reading details) guidance, including a direct alternative tool with usage hint. This fully satisfies the dimension.

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