process_texture_variants

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

The description adds meaningful behavior beyond annotations: it mentions both destructive removal and waiting for processing to settle. This complements the existing destructiveHint=true and idempotentHint=true annotations without contradicting them.

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 a single concise sentence that front-loads the primary action and then adds the wait behavior. Every clause adds information, though 'wait for processing to settle' is slightly vague.

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?

With no output schema, no parameter descriptions, and 4 parameters to handle, the description is not complete enough for an agent to invoke this tool confidently. It fails to clarify how formats, remove, and force interact, and what 'settle' means operationally.

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%, so the description must compensate, but it does not explain the force, remove, or formats parameters. The word 'remove' hints at the remove boolean, but the id, formats, and force semantics remain unspecified.

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 and resource: 'Compress or remove explicit texture variants', which clearly states what the tool does. It distinguishes itself from texture conversion/atlas/metadata siblings by focusing on variant processing, though 'explicit texture variants' is somewhat domain-specific.

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 gives no guidance on when to use this tool versus alternatives such as convert_texture_asset or generate_texture_metadata. It only states the action, not the conditions or exclusions that would help an agent choose it.

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