modifier.apply

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

Annotations already cover read-only, idempotency, and destructiveness. The description adds 'Risk: standard; maturity: L3' and a session-policy note, but it never says what operation literally happens, what scene state changes, or how it treats the input object/modifier. With no real behavioral content, this remains nearly as opaque as the annotation flags.

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 short, but it lacks substance; this under-specification should not be confused with concise, because no meaningful information about the behavior or parameters is front-loaded. The risk and maturity fields are not useful for selecting or calling the tool.

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?

An agent cannot tell from this description what the tool returns, what it modifies, which obstacles a parameter must satisfy, or in which scenes it applies. Although an output schema exists, the surrounding tool is still under-documented and does not provide enough operational context.

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 has 7 parameters but 43% coverage; the description does not explain what any of the parameters mean, especially modifierName and objectId, which are not described in the schema. The description gives no encoder help for the user or agent choosing required values.

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 mostly restates the title as 'PartMe Blender Harness command `modifier.apply`' without saying what the command accomplishes. It never mentions applying a modifier to an object or distinguishes this from the many sibling modifier tools.

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, what to do with it, if another modifier utility would be better, or what conditions invoke it. The only sage advice refers to 'per-request argument checks and session policy,' which does not help choose between alternatives.

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