map_set_bitmap_path

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

Annotations already flag write/destructive behavior (readOnlyHint=false, destructiveHint=true), so the bar is lower. The description adds useful behavioral context by disclosing automatic Bitmaptexture creation when no map is present, but it does not explain what happens to an existing map or how destructive the path replacement is.

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 two short sentences, front-loads the main action, and then states the important auto-creation exception. The bilingual duplication is purposeful and does not add bloat.

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 simple three-parameter mutation with full schema coverage and annotations already flagging destructiveness, the description covers the core operation and the auto-creation side effect. It is missing only explicit alternative tool routing and details about path validation/replacement behavior.

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% and the three parameters are simple strings with clear names/descriptions. The description adds no significant parameter semantics beyond restating the material/slot/path relationship, so the baseline of 3 is appropriate.

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-resource pair ('Set the file path of the bitmap map on a material's slot') and adds the auto-creation behavior ('If there is no map yet, a Bitmaptexture is created automatically'). This clearly distinguishes it from related siblings like map_create_bitmap and mat_set_map_slot.

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 description establishes the context of setting a bitmap path on a material slot, and the auto-creation note implies it can be used on empty slots. However, it gives no explicit guidance on when to prefer this over siblings such as map_create_bitmap or mat_set_map_slot, and no when-not-to-use conditions.

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