remove_modifier

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

The annotations already indicate destructiveHint: true, and the description simply restates the removal action. It does not disclose additional behavioral details such as whether the removal is permanent, what happens if the modifier does not exist, or whether it affects the object's geometry. No extra context is added beyond the annotation.

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 short sentence that immediately conveys the core function. It is front-loaded and contains no filler or redundant information.

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 simple removal tool with an output schema and destructive annotation, the description is mostly adequate, but it omits any mention of error conditions or prerequisites (e.g., object must exist). Given the presence of an output schema, the lack of return-value explanation is acceptable.

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 has no parameter descriptions (0% coverage). The description only clarifies that removal is 'by name', which hints at modifier_name, but it does not explain the role of object_name or any format requirements. This provides minimal help to the agent.

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 ('remove') and the target resource ('modifier'), and specifies the selection criterion ('by name'). This distinguishes it from sibling tools like add_modifier or apply_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?

There is no guidance on when to use this tool versus alternatives, such as list_modifiers or apply_modifiers. No prerequisites or exclusions are mentioned. The only clue is the tool name and bare description.

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