metahuman_link_to_skeleton

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

There are no annotations, so the description is the only behavioral disclosure. It states the operation ('Link...') but does not say whether it mutates existing assets, creates new references, requires a previously imported MetaHuman package, or is idempotent. For a pipeline-modifying tool this is a significant transparency gap.

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 definition is short and front-loaded with the purpose statement, and the example earns its place. The KB line is terse but not bloated, and there are no wasted words. It could reach 5 if the KB pointer were more self-contained, but the structure is otherwise efficient.

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 pipeline tool with seven parameters, no annotations, and no parameter descriptions, the definition is not complete enough for reliable invocation. It covers only the required-parameter example and omits relationships among optional assets, preconditions, and failure behavior. The presence of an output schema and KB link helps but does not fill these 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?

Schema description coverage is 0%, so the description must compensate for the input schema. The example adds real meaning for character_name and body_skeletal_mesh by showing concrete values, but the five optional parameters (ik_rig, retargeter, anim_blueprint, target_skeleton, post_process_anim_blueprint) are left entirely to their names. That partial compensation is insufficient for a 7-parameter tool.

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 first sentence names a specific action ('Link') and a clear resource ('MetaHuman package') with four target asset categories, so an agent can infer what the tool does. The example reinforces the two required inputs. It does not explicitly contrast with sibling metahuman/retargeting tools, so it falls just 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?

No sentence tells an agent when to choose this over siblings such as metahuman_configure_wrapper, create_ik_rig, or setup_full_retargeting_pipeline. The KB pointer and example imply a use case but provide no prerequisites, ordering, or exclusions. This is effectively no guidance beyond the tool's own purpose.

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