import_fbx_animation

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

With no annotations, the description carries the full behavioral burden, but it only states the output attachment target. It does not disclose whether the operation creates nodes, requires an existing parent, overwrites data, or what errors to expect.

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 text is extremely short but fragmentary, using namespace notation and two clipped phrases rather than front-loaded prose. Under-specification rather than conciseness is the issue.

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?

Given the tool has three undocumented parameters, no annotations, and an output schema, the description is too thin. It leaves both the parameter roles and the behavioral side effects largely unexplained.

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 explain the parameters, but it never mentions file_path, name, or parent_path. The vague mention of an attach target is insufficient to clarify even parent_path 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?

The description identifies a specific action (import an FBX animation, Mixamo clip) and resource (kinefx::fbxanimimport), and distinguishes it from the sibling import_fbx_character by focusing on animation rather than character import. The cryptic namespace notation and fragmentary phrasing keep it from being a fully clear 5.

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 one usage prerequisite — attach to a character SOP geo — but provides no guidance on when to choose this tool over import_fbx_character or other animation-related siblings. There are no explicit exclusions or alternative-routing rules.

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