modifier.remove

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

Annotations already indicate non-read-only, non-idempotent, non-destructive behavior, but the description adds only generic risk and maturity labels. It fails to disclose concrete behavioral details such as whether removal is reversible, how it affects the scene revision, or what side effects occur.

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 text is short but under-specified. It front-loads the command name but spends its only sentence on boilerplate risk and maturity rather than useful functional content, so it is terse without being informative.

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 tool with seven parameters majors missing descriptions and no behavioral context, this description is incomplete. It does not explain what removing a modifier entails, what inputs are required, or how this fits with the transaction/session mechanics referenced by the parameters.

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 only 43%, and the description provides no parameter explanations. The key parameters like modifierName and objectId have no descriptions in either schema or description, leaving the agent without guidance on their meaning or format.

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 only restates the command name ('PartMe Blender Harness command `modifier.remove`') and adds risk/maturity metadata. It does not state that this tool removes a modifier from an object, nor does it distinguish itself from sibling modifier tools like blender_modifier_apply or blender_modifier_set_enabled beyond the name itself.

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?

No guidance is given on when to use this tool versus alternatives such as blender_modifier_set_enabled or blender_modifier_apply. The description mentions generic 'requirements' but provides no context about the task it should be chosen for.

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