pipeline_avatar_from_mesh

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

Describes pipeline steps and parameter defaults but lacks explicit disclosure of side effects (e.g., scene modification, object creation, whether it can be undone). No annotations to compensate.

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?

Two introductory sentences followed by a concise parameter list. No wasted words, front-loaded with pipeline 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?

Covers pipeline steps and parameters adequately. Output schema exists, so return value explanation is not needed. Could be improved by noting prerequisites or error handling.

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?

Each parameter is described with defaults and options (e.g., arkit_method enum, export_path default), adding meaning beyond the schema which has no property descriptions.

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?

Clearly states the full avatar pipeline from mesh to FBX with specific steps (validate, armature, weight paint, visemes, ARKit, export). Distinguishes from sibling pipelines that focus on specific tasks.

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?

Implies comprehensive use but no explicit when-to-use or alternatives compared to other pipeline tools. Agent must infer from name and context.

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