rig-parent_with_auto_weights

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

With no annotations, the description carries the full burden for disclosure. It clearly indicates a mutating operation (parenting plus automatic weight generation), but it does not mention side effects such as whether existing vertex groups are overwritten or if an Armature modifier is added. This is acceptable but not richly transparent.

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 sentence that efficiently communicates the core operation. There is no filler, repetition, or unnecessary detail.

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 simple two-parameter tool with no output schema, the description sufficiently covers what the tool does and what it operates on. It could mention prerequisites or side effects, but the low complexity means the current level of detail is mostly adequate.

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 schema has no property descriptions, only titles, and the tool description does not elaborate on the two parameters. However, the titles 'Mesh object to skin' and 'Armature object to bind the mesh to' plus the parameter names make the intent reasonably clear, so the low coverage is partially mitigated.

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 tool's action: 'Parent a mesh to an armature with automatic skinning weights'. It uses a specific verb and resource, and 'automatic skinning weights' distinguishes this tool from generic outliner parenting or pure weight-assignment rig 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?

The description implies when to use it: when you want to bind a mesh to an armature using automatic skinning weights. However, it does not explicitly name alternatives or explain when not to use it, such as when manual weight painting or simple parenting is more appropriate.

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