Create or resize the texture

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real behavioral context beyond them: resizing anchors old pixels at the top-left, and UV size is a side effect unless set_uv_size is false. It stops short of explaining overwrite semantics for an existing texture name, which is what makes the destructive hint material.

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?

Two front-loaded sentences with no filler; the create/resize duality comes first and the UV side effect second, with the pixel-anchoring detail earning its clause.

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 six-optional-parameter mutation tool with no output schema, the description covers the main modes and side effects but leaves open whether an existing texture with the same name is replaced, what a caller gets back, and which parameters are required to create versus resize.

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 schema already documents fill, name, width/height, keep_pixels and set_uv_size. The description only restates the set_uv_size toggle and the top-left anchoring, adding little parameter-level meaning beyond the schema.

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 ('Creates the project texture, or resizes it') and includes the secondary effect on project UV size. This clearly separates it from texture_import (bring in external image) and texture_set_pixels/fill_rect (modify existing pixels), though no sibling is named explicitly.

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 two modes (create vs resize) are described, implying when each applies, but there is no explicit guidance on when to prefer this over texture_import or over setting pixels directly, and no mention of prerequisites such as whether the texture must already exist for the resize path.

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