import_fbx_character

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

No annotations are provided, so the description carries the full disclosure burden, yet it discloses almost nothing behavioral: no mention of side effects (what nodes it creates), error modes on bad paths, or how the rest-pose handling affects the rig. The only hint ('under mcp_* geo') is about placement, not 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?

It is very short, which is good, but the telegraphic fragment style front-loads an internal node identifier rather than the user-facing action. Brevity here trades against comprehension instead of earning its place.

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?

With an output schema present, return values need not be explained, but the description still leaves key gaps: undocumented parameters, no annotation coverage, and no statement of what gets created or where. For an import tool with a required file path, this is under-specified.

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?

All three parameters have 0% schema description coverage, so the description must compensate and largely doesn't. It loosely implies a target network (relevant to parent_path) and an FBX source (relevant to file_path), but the name parameter and default values are never explained.

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 name gives a clear verb+resource, and the description adds the underlying Houdini node type (kinefx::fbxcharacterimport) and network scope (mcp_* geo). However, it never plainly states that it imports a skeletal/character FBX into the scene, and the phrase 'Mixamo/character rest pose' is cryptic rather than explanatory. An agent can roughly infer intent but not confidently.

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?

There is no when-to-use guidance and no routing among obvious siblings such as import_fbx_animation, attach_kinefx_deform, or map_kinefx_joints. The agent is left to guess whether this is the entry point for rigged character import versus animation import.

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