parent_mesh_to_armature

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

With no annotations, the description must carry the full behavioral burden. It does reveal weight behavior with 'AUTOMATIC (auto weights)' and 'EMPTY (no weights)', but it does not disclose side effects such as whether existing armature modifiers are replaced, whether EMPTY still creates a modifier, or whether AUTOMATIC is computationally expensive. This leaves important behavioral ambiguity.

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 two short sentences with no filler. The core action is front-loaded, and the mode definitions are compact and useful. Every word earns its place.

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?

The description is too thin for a mutation tool with no annotations and 0% schema parameter coverage. It does not address prerequisites, side effects, or how this differs from sibling parenting tools. The presence of an output schema helps only with return values, not with the missing behavioral and usage context.

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 description coverage is 0%, so the description must compensate. It explains the mode parameter and its two values, but it adds no meaning to the mesh or armature parameters beyond their names. The agent still does not know whether these expect object names, IDs, or something else.

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 operation: 'Parent a mesh to an armature.' It names a specific verb, resource, and target, and the mode breakdown adds important scope. This distinguishes it enough from the generic sibling set_parent and clear_parent.

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?

There is no guidance about when to use this tool versus alternatives like set_parent or clear_parent. The mode descriptions give some parameter-level direction, but the description never states prerequisites, exclusions, or the difference between this and generic parenting tools.

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