blender_generate_texture

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

Annotations only say readOnly=false, idempotent=false, destructive=false. The description adds the key side effect: it writes a real PNG to disk and clarifies the result is a normal, inspectable, shippable file, not a viewport-only effect. It does not mention overwrite behavior or datablock creation, but it adds meaningful behavior beyond annotations.

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 two short paragraphs, front-loaded with the action and output. The 'useful for' list is relevant and the final sentence adds behavioral clarity without padding. Every sentence earns its place.

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 13-parameter tool with no output schema, the description plus rich schema covers the essentials: what it produces, where it writes, and that it is a real file. It does not describe the response payload, but the response_format parameter and schema descriptions fill most gaps.

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 92%, so the schema already documents nearly all parameters. The description adds a little color by naming example patterns that map to the pattern enum, but it does not explain parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Generate a procedural texture and write it to a real PNG on disk.' It clearly distinguishes the tool from viewport-only effects and, combined with the listed use cases, makes the function 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?

The description gives concrete use cases ('plate text, hazard stripes, carbon weave, rust, brushed metal, leather grain and similar'), which implies when to use the tool. However, it does not state when to prefer a sibling like blender_bake_texture or blender_generate_pbr_set, nor does it provide exclusions.

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