Create mesh warp

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

Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) indicate the tool creates non-destructive open-world elements. The description adds detail by stating it builds a Geometry COMP, applies textures, renders, and outputs a Null, which aligns with and enriches the annotations. No contradictions.

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 (3-4 sentences), front-loads purpose, and every sentence adds essential information without redundancy. It efficiently covers purpose, components, and output.

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 complex tool that constructs a multi-node setup, the description covers the main components (Geometry COMP, grid, MAT, Camera, Light, Render, Null) and the output. It lacks explicit mention of prerequisites (e.g., source TOP must be a valid path), but the schema already provides that context. Overall, it is fairly 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 high (86%). The description adds marginal value beyond schema: it explains rows/cols affect smoothness and weight, and mentions 'Expose a Zoom knob' for expose_controls. Most parameter details are already in the schema, so minimal extra meaning.

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 tool maps a source TOP onto curved surfaces via a deformable grid, explicitly distinguishing it from sibling 'create_projection_mapping' as a curved-surface upgrade. The verb 'Map' and resource 'source TOP onto curved surface' are specific and unambiguous.

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 indicates when to use this tool ('for domes, columns, and sculptures') and positions it as an upgrade to create_projection_mapping's flat corner-pin, implying its use for curved surfaces. However, it does not explicitly state when NOT to use it or list other alternatives.

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