Add a Rigify metarig for rigging. Offers presets for human, basic_human, quadruped, cat, wolf, horse, shark, and bird.
添加 Rigify 元骨架：human/basic_human/basic_quadruped/cat/wolf/horse/shark/bird。
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| type | No | human |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates the tool adds a metarig, implying scene modification, but does not mention side effects like object creation or whether it replaces existing rigs. No annotations to supplement.
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 a single concise sentence, directly stating the purpose and listing types without any extraneous content.
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?
While the core action and types are clear, the description omits details about the 'name' parameter and any prerequisites or effects, making it relatively complete for a simple add operation but not fully comprehensive.
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?
The description lists possible values for the 'type' parameter, but does not explain the 'name' parameter or its purpose; schema provides no descriptions either.
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 the action (add a Rigify metarig) and enumerates the supported types, distinguishing it from related rig-generation tools.
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 explicit guidance on when to use this tool versus alternatives like generate_rigify_rig; it only lists metarig types, not usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.