set_material_3d

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly reveals that omitted params reset to class defaults and that it replaces any previous override, which are key behavioral traits. It stops short of detailing side effects like texture loading or reversibility, but the core behavior is transparent.

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 a single, well-structured sentence that front-loads the main action and then adds critical behavioral details after the dash. Every word contributes value, with no fluff or repetition.

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 mutation tool with no annotations and 15 parameters, the description provides the essential conceptual model: it creates a fresh material, resets omitted parameters, and replaces previous overrides. It does not cover return values (no output schema exists) or specific per-parameter interactions, but the core semantics and the required node_path are indirectly clear. Minor gaps prevent a perfect score.

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 0%, so the description must compensate for parameter meaning, but it does not explain any of the 15 parameters. The generic statement about omitted params resetting to defaults is helpful at a high level, but it leaves all specific parameter semantics (e.g., cull_mode, emission_energy) to the schema, which only provides names and types, not operational 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 specific action: setting a fresh StandardMaterial3D as a MeshInstance3D surface override. It uses a specific verb and resource, and distinguishes itself from sibling material tools like assign_shader_material by emphasizing 'fresh StandardMaterial3D' and 'surface override'.

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 implies clear usage context: use when you need to apply a new StandardMaterial3D to a MeshInstance3D surface, especially replacing an existing override. It does not explicitly list alternatives or when-not-to-use, but the context is strong enough to guide selection among siblings.

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