render_material_variations

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

With destructiveHint=true already declared, the description adds real value by disclosing that the original graph state is restored after rendering, softening the destruction risk. It also discloses the 64-combination cap and the mode-dependent outputs (preview PNGs vs. per-manifest results), going beyond what annotations convey.

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?

Three tight sentences with the core purpose and the state-restoration guarantee front-loaded, followed by the complex parameter format and the mode distinction. Every sentence earns its place, with no redundant restatement of the name.

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 an 8-parameter, nested, destructive tool this is only partially complete. The nested variations structure and state restoration are covered and the output schema covers manifests, but the semantics of mode, size, model, profile, rotation, and material_id remain unexplained anywhere.

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 coverage is 0%, so the description carries full burden. It explains the most complex parameter (variations) thoroughly with a concrete nested example, and describes mode behaviorally, but leaves six other parameters — including the required output_dir plus size, model, profile, rotation, and material_id — completely undefined.

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 and resource — render parameter combinations and restore the graph state — and quantifies scope with 'up to 64'. However, it never distinguishes this from the very similarly named sibling preview_material_variations, leaving an agent to infer the boundary.

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?

Usage is only implied: 'Preview mode writes 3D preview PNGs; export mode writes the selected profile' hints at which mode fits which goal but never states when to choose this tool over preview_material_variations or render_node. No prerequisites or exclusions are given.

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