unity_configure_pipeline

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions that blueprint_json uses intelligent defaults if empty, but does not describe side effects, permissions required, or what happens to existing assets. For a pipeline that likely modifies the scene significantly, this is insufficient.

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 extremely concise: a one-sentence summary, then a list of parameters with brief explanations. Every sentence adds value, and the structure is front-loaded with the essential purpose.

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 covers the tool's high-level purpose and all parameters. However, it does not mention the return value or output schema, which exists. Given the complexity of the pipeline, a brief note on what the tool returns would enhance completeness.

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?

Although the input schema has 0% description coverage, the description adds meaningful explanations for all four parameters, including the optional blueprint_json override behavior. This compensates well for the schema's lack of detail.

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 that the tool performs a one-click full Unity avatar setup pipeline, enumerating specific steps (import FBX, configure humanoid rig, set up avatar descriptor, create expression menu/params, configure materials). This distinguishes it from sibling tools that handle individual steps.

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 implies it is a comprehensive pipeline for avatar setup, but does not explicitly state when to use it versus using individual sibling tools (e.g., unity_import_fbx, unity_setup_avatar_descriptor). No when-not-to-use or alternative guidance is provided.

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