entity_set_material

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, covering the safety profile. The description adds a genuine side-effect detail (faces scope makes instances unique first), but omits whether existing material is overwritten, what path/color do, and permission requirements.

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 tight sentences with the primary action front-loaded and no filler. It is efficient, though the second sentence could be clearer about the mechanism rather than just stating an outcome.

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?

A mutation tool with six parameters, no output schema, and 0% schema coverage needs more than two short sentences. The interaction with existing material, the role of path/color, and return behavior are all unaddressed.

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 carries the full burden for six parameters. It only implicitly touches the scope enum (instance vs faces) and material, explaining nothing about path, color, model_id, or entity_id, leaving most parameters opaque.

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?

States a specific verb (assign) and resource (material) plus the target (instance or its direct faces), so the core operation is clear. However, it does not differentiate from siblings like materials_set or entity_update, leaving the agent to guess which tool owns material assignment.

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 or when-not-to-use guidance and no alternative named. The scope note implies behavior but gives no condition that tells the agent to pick this tool over materials_set or entity_update.

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