set_fabric_texture

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation but does not disclose whether the existing texture is replaced, whether the operation is undoable, what file access or permissions are required, or what happens on errors.

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 no wasted words. Its brevity is efficient, though the under-specification is a separate completeness issue.

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 mutation setter with no annotations, no output schema, and fully undocumented parameters, the description is too sparse. An agent lacks the context needed to select and invoke it correctly relative to sibling fabric tools.

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% with two parameters. The description adds only that file_path should be a PNG or JPG image; it gives no meaning for fabric_index (e.g., index from get_fabric_list, zero- or one-based) or how file_path is resolved.

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?

States a specific verb and resource ('use an image as a fabric's base texture'), and the 'base texture' framing helps distinguish it from color/plaid siblings. However, it does not explicitly differentiate itself from other fabric-modifying tools like set_fabric_faces or apply_fabric_json.

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?

No when-to-use, prerequisites, or alternatives are provided. It does not say to use set_fabric_color for solid colors or apply_plaid for plaid patterns, nor does it state that fabric_index must reference an existing fabric.

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