parent_mesh_to_armature

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

With no annotations, the description carries the full burden of behavioral disclosure. It does explain the two mode behaviors (auto weights vs. no weights), but it does not disclose side effects such as whether existing vertex weights are overwritten, whether the previous parent is replaced, or any prerequisites. This is minimal behavioral context for a potentially destructive operation.

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 exceptionally concise: two short sentences that front-load the core purpose and then detail the mode options. Every word earns its place, with no redundant or tangential 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?

For a rigging operation with no annotations and no parameter descriptions in the schema, the description is too thin to be complete. It omits prerequisites (e.g., armature must have a pose, mesh must be selected), what happens to existing parenting or weight groups, and possible error conditions. The mode information is helpful but does not compensate for these significant gaps.

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 adds meaningful semantics for the 'mode' parameter, explaining what AUTOMATIC and EMPTY do. However, with 0% schema description coverage, mesh and armature parameters are left entirely undocumented, although their purposes are mostly inferable from their names. The mode explanation provides some value beyond the schema.

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 'Parent' and the resources 'mesh' and 'armature', and it provides distinct mode options ('AUTOMATIC' vs 'EMPTY') that differentiate it from the generic sibling tool 'set_parent'. However, it does not explicitly contrast itself with other parenting tools, so it stops short of full differentiation.

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 gives no explicit guidance on when to use this tool versus alternatives like 'set_parent' or clear_parent. The mention of modes implies a rigging/skinning context, but there is no stated exclusion or recommendation about which tool fits which scenario.

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