unity_import_fbx

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

The description lists actions (copy, set rig, extract materials/textures) and parameters, but lacks details on what happens on file conflicts, folder creation, error handling, or whether it overwrites existing settings. Since no annotations are provided, the description carries the full burden and does not fully disclose behavior.

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 concise with a summary line and parameter list. Every sentence adds value. Could be slightly more structured with separate sections, but overall 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?

Given the complexity of FBX import with multiple settings, the description covers main actions and all parameters with defaults. The output schema exists, so return values are not needed. Missing details on error conditions and prerequisites, but adequate for basic understanding.

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?

With 0% schema description coverage, the description adds meaning by listing each parameter with a brief explanation (e.g., 'If empty, uses UNITY_PROJECT_PATH'). This compensates well, though some parameters like destination could benefit from format details.

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 'Import an FBX file into a Unity project and configure import settings' with specific actions (copies FBX, sets humanoid rig, extracts materials/textures). This clearly distinguishes it from generic import tools like io_import_file or other Unity-specific tools.

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 for FBX import with specific settings but does not explicitly state when to use this tool versus alternatives like io_import_file or other Unity tools. No prerequisites or exclusions are mentioned.

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