rig.parent_with_auto_weights

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

The description discloses the key behavior: automatic skinning weights. However, it lacks details on side effects (e.g., modification of modifiers, vertex groups), prerequisites, or error conditions. With no annotations, the burden is higher, and the description only partially meets it.

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, front-loaded sentence that conveys the core functionality without extraneous words. It is appropriately sized for the tool's simple 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?

For a mutation tool that modifies scene data, the description is too brief. It omits crucial information such as return value, error conditions, behavior with invalid parameters, and the effect on existing parenting or vertex groups. With no output schema or annotations, completeness is insufficient.

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 property titles provide basic meaning ('Mesh object to skin', 'Armature object to bind the mesh to'), but the description itself adds no further explanation. With 0% schema description coverage, the description should clarify parameter roles and constraints, which it does not.

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 explicitly states the action ('Parent') and the objects involved ('mesh to an armature'), and specifies the outcome ('with automatic skinning weights'). This clearly distinguishes it from sibling tools like rig.assign_weights (which only assigns weights) or rig.add_armature (which creates armatures).

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 versus alternatives. Missing prerequisites (e.g., mesh must be unparented, armature must have deform bones) and no mention of when not to use it. Given siblings like rig.assign_weights, explicit usage direction would be helpful.

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