material.assign

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

Annotations are all false and the description carries the full burden of behavioral disclosure, yet it only gives 'Risk: standard; maturity: L3.' It never states that this is a mutating operation, what scene changes occur, or what side effects to expect. This is effectively no behavioral transparency.

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 extremely short, but this is under-specification rather than conciseness. The sentence spends characters on 'PartMe Blender Harness command' and generic risk/maturity metadata instead of explaining the tool's function.

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 tool with required parameters, a mutation effect, and many material-related siblings, the description is missing the core behavior, side effects, and selection criteria. An output schema exists, but it does not compensate for the complete absence of functional context.

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 only 50%, and the description does not compensate by explaining `object` or `material`. It mentions no parameter semantics at all, leaving the agent to infer meaning from parameter names alone.

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 only restates the command name `material.assign` and does not say that it assigns a material to an object. It lacks a specific verb+resource statement and cannot be distinguished from other material tools based on the description alone.

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 only usage-related content is 'Requirements: Per-request argument checks and session policy still apply,' which is generic and does not say when to use this tool versus siblings like blender_material_attach_image_texture or blender_material_create_pbr. No context, prerequisites, or alternative routing is provided.

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