apply_modifier

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

The description discloses that the effect is permanent and modifies geometry, implying irreversibility. However, with no annotations, it misses details like undo behavior or required permissions. Basic transparency, not comprehensive.

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 sentence with 11 words, very concise. It front-loads the core action. However, it sacrifices necessary details for brevity in the context of missing annotations.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description is too minimal to fully inform the agent. It covers the action but omits parameter semantics and usage context, leaving significant gaps.

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?

No parameter descriptions are provided in the schema (0% coverage) and the description does not explain what 'name' or 'modifier_name' refer to. The agent must infer meanings from context, which is insufficient.

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 (apply a modifier) and the effect (permanently bake into mesh geometry). It distinguishes from adding a modifier, but does not differentiate from the sibling tool 'modifier_apply', which likely has similar purpose.

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 on when to use this tool versus alternatives like 'modifier_apply' or 'modifier_apply_all'. The description does not mention prerequisites or context for use.

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