configure_texture

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

Discloses that changes are persisted, triggers UE's PreEditChange/PostEditChange flow, and rebuilds the GPU resource. This goes beyond the basic mutation fact, highlighting resource-intensive side effects. Since no annotations are provided, these behavioral details are essential and well-covered.

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 sentences, no redundancy. The first sentence defines purpose and scope, the second adds behavioral context. Every word is necessary; there is no fluff.

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 tool with no output schema and 6 parameters, the description covers purpose, behaviors, and side effects adequately. It does not mention return value (likely success/failure), but that is minor for a mutation tool. Overall complete given the complexity.

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?

Input schema has 100% description coverage, so the baseline is 3. The description does not add significant meaning beyond the schema, merely confirming that the listed properties are adjustable. No additional parameter constraints or formatting details are provided.

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?

Clearly states it adjusts SRGB, CompressionSettings, LODGroup, and Filter on an existing UTexture asset, which matches the input schema properties. The verb 'Adjust' and resource 'existing UTexture asset' precisely describe the action, distinguishing it from creation (import_texture) or inspection (inspect_texture) tools.

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?

Implies usage for modifying existing textures (not creating or reading), but does not explicitly state when to use versus alternatives like import_texture or inspect_texture. No mention of prerequisites, when not to use, or specific context beyond asset existence.

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