maya_unreal_import_fbx

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

The description warns about potential axis/scale issues that can produce rotated or scaled meshes and advises verifying via viewport capture. It also highlights reading `warnings` from the return value. Despite lacking annotations, it does not explicitly state that the import permanently modifies the scene or is undoable, but the parameter explanations for merge modes imply side effects.

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 well-structured with an intro, scope note, and a parameter list. No redundant sentences; each part serves a purpose.

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 complexity (6 parameters, no annotations, no output schema), the description covers purpose, limitations, usage steps, and all parameter semantics. It could also mention error conditions or prerequisites, but it is largely complete for an import tool.

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?

The schema has no parameter descriptions, so the description fully compensates by explaining each parameter: path, namespace, group, up_axis, scale_factor, and import_mode with its options. It adds practical guidance such as retrying with 'z' if the result is rotated and using namespace when names conflict.

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 'Imports FBX into current Maya scene' and identifies this as the path for receiving Unreal level assets. It also explicitly excludes exporting from Unreal, distinguishing it from the sibling maya_unreal_export_fbx.

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 provides context that this tool is for importing manually exported FBX files and notes that Unreal-side export is out of scope. It instructs to verify results with maya_viewport_capture and read warnings, giving practical usage guidance. However, it does not explicitly name alternative tools for related tasks.

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