blender_iso_create_avatar

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

With no annotations, the description carries the full burden and does disclose the main chain: procedural geometry, rendering, and sprite generation. But it is silent on consequential side effects such as whether it mutates or clears the current Blender scene, whether repeated runs accumulate or replace objects, whether it writes files to outputDirectory, and whether it depends on prior scene or material setup.

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?

Single front-loaded sentence with the core verb chain first and no filler. The long modifier tail ('2:1 dimetric NPR stylized... beveled hair, layered clothing') is dense, but each element adds operation-relevant information and would be genuinely useful to an agent.

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 12-param procedural pipeline with zero annotations, no output schema, and 0% parameter documentation, the description leaves material gaps: prerequisites, scene-state effects, output file details, and how the step relates to blender_iso_render_turnaround and blender_iso_setup_scene. An agent can form an intention but not a safe, unambiguous invocation plan.

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. It loosely maps to the palette color parameters via 'customizable palette' and to the directions parameter via '8-direction,' but adds no meaning for scale, name, baseName, tileWidth, tileHeight, or outputDirectory. Its blanket '8-direction' claim also understates the directions enum's 4-or-8 choice.

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 chain ('builds and renders') on a concrete resource ('2:1 dimetric NPR stylized humanoid avatar in Blender') plus a deliverable ('8-direction turnaround sprites'). However, it never distinguishes itself from the sibling blender_iso_render_turnaround, which appears to cover the same rendering/turnaround step, so an agent cannot rule out that sibling from the description alone.

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?

Offers no when-to-use or when-not-to-use guidance and names no alternatives, despite nine siblings including blender_iso_setup_scene (a likely prerequisite), blender_iso_apply_npr_material (NPR styling), and blender_iso_render_turnaround (rendering). The implicit reading that this is the all-in-one avatar path is plausible but unverified, leaving workflow sequencing and delegation to the agent's guesswork.

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