create_anim_composite

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

Annotations already declare readOnlyHint=false and idempotentHint=true. The description adds valuable detail beyond annotations: an existing asset at the path is returned unchanged with already_existed=true and saved=false, and a failed save yields success false, saved=false, and save_error. It does not cover permissions or rate limits, but those are not implied by the 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 three tight sentences: purpose, idempotent contract, failure mode, followed by a compact return-field list. It is front-loaded, with no redundant or wasted wording.

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 creation tool with no output schema, the description is nearly complete: it states the asset type, location, idempotent behavior, failure behavior, and return fields. A minor gap is that it does not clarify what happens if the optional skeleton_path is omitted or how the default package_path is applied.

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 100%, so name, package_path, and skeleton_path are already documented in the schema. The description adds only that the asset is under /Game and bound to a USkeleton, which aligns with but does not extend the schema's parameter semantics.

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?

States a specific verb and resource: 'Create and save a UAnimComposite asset bound to a USkeleton, under /Game.' It names the asset type and binding, clearly distinguishing it from siblings like create_anim_sequence, create_anim_montage, and create_blend_space.

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 usage by naming the asset type and gives idempotent behavior for existing assets, but it does not explicitly say when to choose this over sibling creation tools such as create_anim_sequence or create_anim_montage. No exclusions or alternatives are named.

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