save_material_preview

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

Annotations already declare this as a non-read-only, destructive, non-idempotent write, so the safety profile is carried by structured fields. The description adds that the captured content is the rendered 3D PBR preview in PNG, but does not disclose what the destructive behavior actually means (overwriting an existing file at path) or how material_id/rotation select what is rendered.

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?

A single tight sentence with the action and output front-loaded and no wasted words. Nothing could be cut without losing information.

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?

The output schema means return values need no explanation, but for a 6-parameter destructive file-writing tool the description gives almost no parameter or behavior detail. An agent cannot determine required inputs, defaults, or overwrite semantics from the description alone.

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?

All 6 parameters have 0% schema description coverage, so the description carries the full burden and does not meet it. It never mentions that path is required and is the write target, that model defaults to a sphere, that width/height control the saved image, or what material_id and rotation select — the PNG/3D hints only weakly imply width/height.

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 names a specific verb (save) plus the resource (Material Maker's 3D PBR preview) and the output format (PNG), which separates it from siblings like save_material (saves the material itself) and preview_material_maps (2D maps). It stops short of naming any sibling explicitly, so an agent must infer the distinction.

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 when-to-use statement, no prerequisites, and no reference to alternatives such as preview_material, preview_material_maps or export_material. The agent must infer that this tool is for writing a raster preview rather than inspecting or exporting the material.

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