Edit texture properties

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. 'Change' implies mutation, but nothing is said about whether changes are persisted/undoable (bb_undo exists as a sibling), what permissions or active context are required, or what happens to unspecified fields. Listing 'saved' as a settable field is also odd and unexplained.

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 tight sentence that front-loads the verb and resource, which is efficient. However, the field list is a bare enumeration that both misses a schema parameter and includes a non-existent one, so the brevity comes at the cost of accuracy.

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 9-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is far too thin. It should at minimum explain the required 'targets' argument, the omitted 'keep_size' flag, and persistence/undo 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 0% across 9 parameters, so the description is the only source of parameter meaning. It enumerates 8 fields but omits 'keep_size' and 'targets' (the sole required param) and mentions 'saved', which is not in the schema — a partial, partly inaccurate mapping.

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 ('Change') and resource ('texture metadata') and enumerates the editable fields, so the agent knows what the tool does. It does not distinguish itself from related siblings like bb_set_face_texture or bb_create_texture, which is the only thing keeping it from a 5.

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 versus bb_set_face_texture, bb_create_texture, or bb_draw_texture, nor any stated prerequisites (e.g. whether a texture must already exist). The agent must infer all routing from the name alone.

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