duplicate_anim_sequence

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds substantial behavioral context beyond them: atomic refusal on any name collision ('nothing is touched'), the StaticDuplicateObject mechanism, same-skeleton constraint, and the failed-save outcome (saved=false, save_error, copy remains memory-only).

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 action is front-loaded and most sentences carry weight, but the return keys are stated twice ('Returns duplicate_path and duplicate_class.' followed by an explicit 'Returns: {...}' line), which is redundant. Slightly heavy run-on first sentence but not wasteful overall.

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?

No output schema exists, so the description correctly supplies the return shape and failure semantics. One minor gap: it mentions a 'success' flag in prose but the enumerated return keys (source_path, duplicate_path, duplicate_class, saved, save_error) omit it, a small internal inconsistency an agent may notice.

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 coverage is 100%, so 3 is the baseline. The description adds a real constraint not present in the schema: new_name must not collide with any asset in memory or on disk, including the source. That is meaningful parameter semantics beyond the schema's plain field descriptions.

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 states a specific verb (Copy/duplicate), the exact resource (UAnimSequence), and the target naming scheme (package_path/new_name). It explicitly distinguishes itself from duplicate_asset for non-AnimSequence assets, so an agent can route without opening a schema.

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?

It gives an explicit when-not with a named alternative: 'For other asset types use duplicate_asset.' Combined with the AnimSequence scope and the uniqueness precondition, the agent knows both when this tool applies and where to go otherwise.

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