set_texture

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

Clearly states that modifications are runtime-only and lost on reload, which is beyond the annotations (destructiveHint true, idempotentHint true). Adds critical behavioral context about persistence and user consent.

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 relatively short but contains repetition (runtime preview mentioned twice). It is front-loaded with the key purpose and behavioral constraint, earning its sentences, though slight redundancy prevents a 5.

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 tool with 12 parameters and no output schema, the description provides essential contextual completeness by highlighting the temporary nature and the need to ask the user. It does not cover all parameter nuances but leverages the schema descriptions sufficiently.

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 covers 100% of parameters with descriptions. The tool description only generically lists property names ('wrap, filter, anisotropy, repeat, offset, colorSpace') without adding new semantics or usage details 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?

The description clearly states the tool modifies texture properties with a specific list of properties. It distinguishes itself from sibling set_* tools by focusing on texture and adding the runtime preview context, making the purpose unambiguous.

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?

Explicitly instructs to ask the user first, differentiating between runtime preview and persistent code change. This provides clear when-to-use and when-not-to-use guidance, with implied alternatives.

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