apply_modifier

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

No annotations are provided, so the description carries the full burden. It mentions 'collapsing it into the mesh data,' implying a destructive operation, but does not explicitly warn about irreversibility or side effects on the modifier stack.

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 concise with two sentences and a bullet list, front-loading the main action. No unnecessary information is present.

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 description adequately explains the action and parameters. It mentions the outcome ('collapsing it into the mesh data') but does not specify what happens after application (e.g., feedback, modifier removal from stack). For a simple mutation, this is mostly complete.

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%, but the description adds full context: 'name: Object name' and 'modifier_name: Exact modifier name as shown in Blender's Properties panel.' This provides necessary guidance beyond the schema.

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 that the tool applies a named modifier on a mesh object and collapses it into the mesh data. The verb 'Apply' and resource 'modifier on mesh object' are specific, and it distinguishes from sibling tools like 'add_modifier'.

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 implies when to use (to apply a modifier) but does not explicitly state when not to use or mention alternatives like 'add_modifier'. No guidance on prerequisites or exclusions is provided.

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