apply_mesh_solidify

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds useful context: it explicitly says the mesh is replaced, which is the concrete destructive effect, and documents the return fields (triangle counts, vertex count, solidified flag) that are not in an output schema. It does not cover performance expectations or reversibility 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?

Two concise sentences: the first front-loads the action and effect, the second compactly declares the return shape. No wasted words.

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?

With no output schema, the description helpfully supplies the return object shape. Annotations cover the safety profile, and the schema covers all parameters. The only gap is the lack of guidance on alternatives/caveats, which is partially covered by the purpose statement.

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 100%, so all six parameters are documented in the schema itself. The description adds no parameter-level semantics beyond what the schema provides, so the baseline score of 3 applies.

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 gives a specific verb ('Voxel-wrap') and target ('DynamicMeshActor's dynamic mesh'), plus a parenthetical clarifying the transformation ('replaces the mesh with a voxelised-and-meshed approximation'). This clearly distinguishes it from sibling remesh/simplify/boolean 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?

The description states what the tool does but gives no guidance on when to use it versus alternatives such as apply_uniform_remesh, apply_adaptive_remesh, or simplify_mesh. No prerequisites, when-not-to-use, or selection criteria are provided.

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