pipeline_blender_to_unity

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

Without annotations, the description carries full burden. It lists procedural steps but does not disclose behavioral traits such as destructiveness, idempotency, file overwrites, or required Unity environment state. This is insufficient for an agent to understand side effects.

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 concise with three short paragraphs: overall purpose, detailed chain, and parameter list. It is front-loaded with the main idea but the chain detail slightly repeats the high-level summary.

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?

The description explains inputs but omits output behavior (despite output schema existing) and prerequisites like Unity project state. For a complex pipeline, this leaves gaps in understanding for the agent.

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?

Despite 0% schema coverage, the description provides clear one-line explanations for each parameter and notes the conditional dependency of physbones_json on setup_physbones. This adds meaningful context beyond parameter names.

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 it is a Unity-side pipeline for FBX imports, avatar descriptor, expressions, and build. It distinguishes itself from sibling tools like unity_import_fbx or unity_setup_avatar_descriptor by encompassing the entire chain, and from other pipelines like pipeline_avatar_from_mesh by specifying FBX input.

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?

No guidance is provided on when to use this tool vs. individual Unity tools or other pipeline tools. There is no mention of prerequisites, when-not-to-use, or alternatives.

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