mat_rename

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

The annotations already indicate readOnlyHint=false and destructiveHint=true, but the description adds no behavioral context beyond the bare operation. It does not mention side effects such as reference updates, undo behavior, or error conditions, so it provides no value beyond the structured annotation.

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 concise, with exactly one meaningful sentence repeated in both Chinese and English. There is no wasted text, and the operation is front-loaded clearly.

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's low complexity, fully documented parameters, and annotations covering the safety profile, the description is mostly adequate. However, with no output schema, it does not state what the tool returns, and it omits any mention of side effects or prerequisites, leaving minor gaps for an agent.

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 100%, so the input schema already fully documents the 'material' and 'name' parameters. The description adds no additional semantic detail about parameter formats, uniqueness constraints, or naming rules; the baseline of 3 applies.

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 verb 'Rename' and the resource 'a material', which distinguishes it from object-rename tools in the sibling list. However, it does not explicitly contrast with similar material operations like mat_set_property, so it falls short of full sibling differentiation.

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 about when to use this tool versus alternatives such as mat_set_property or rename_object. The description only says what it does, not when to choose it, leaving the agent to infer usage from the tool name alone.

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