batch_apply_material

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

With no annotations and a minimal description, there is no disclosure of side effects, whether existing materials are replaced, or how the operation behaves on multiple objects. The description provides no behavioral insight.

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, which makes it concise, but it lacks structure and essential information. It is more of a label than a functional description, so it is not effectively front-loaded with useful content.

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?

Given the tool has two required parameters and no output schema, the description should clarify how to invoke it correctly. It does not address parameter formats, prerequisites, or typical use cases, leaving the agent under-informed for correct invocation.

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?

The parameters 'objects' and 'material' are named but not explained. The 'objects' field has a complex union type (array, object, string) with no clarification of accepted forms, and 'material' is ambiguous (name, ID, or path). The description adds no semantic value.

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 '批量赋材质' conveys the core action of batch-assigning materials, but it is a bare phrase without context. It does not specify scope or differentiate from the sibling tool 'assign_material', leaving the purpose only partially clear.

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 tool versus alternatives like 'assign_material' or 'create_material'. The description offers no situational context or selection criteria.

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