material_set_group

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

Annotations already declare destructiveHint=false, readOnlyHint=false, and closed-world scope, so the safety profile is covered. The description adds one genuinely useful behavioral detail — passing '' removes the material from any group — but says nothing about failure modes (unknown material name, nonexistent group, case sensitivity).

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 front-loaded sentence with the core action first and the sentinel-value caveat in parentheses. Nothing is wasted, though the parenthetical is terse enough to be slightly cryptic.

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?

An output schema exists, so return values needn't be explained, and annotations cover the mutation profile. Still, for a two-parameter tool with zero schema documentation, the description leaves the identity of `name` unclear and omits what happens when the group doesn't exist.

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 carry parameter meaning, and it only partly does. It explains the empty-string sentinel for `group`, but never states that `name` is the material to move (vs. the group name), leaving the most important parameter implicit.

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 uses a specific verb ("Move") and resource ("a material into a material group"), which is far clearer than a name restatement. It doesn't explicitly differentiate itself from adjacent siblings like material_set_field or material_assign, but the group-targeting purpose is 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?

There is no guidance on when to use this versus material_assign or the other material_set_* tools, and no prerequisites are stated. It also doesn't say whether the target group must already exist or will be created on the fly.

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