ghostrigger_import_to_ue5

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

No annotations are provided, so the description carries the burden. It discloses that this is a multi-step operation (calls GhostRigger then UE5), that it writes an FBX file, and that it imports into the Content Browser. It also documents the return JSON structure. It doesn't mention failure modes or side effects like overwriting existing assets, but the step disclosure and return format are solid.

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 numbered steps, a clear Args list, and a Returns section. It's longer than average but every section earns its place given the multi-step nature. The example is slightly confusing (uses '/Game/MCP_Test/Example' as export_path, which looks like a UE5 path rather than a filesystem path), but overall it's organized and front-loaded.

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?

The description covers the pipeline steps, parameter semantics, return format, and even points to a knowledge base article. It lacks explicit error-handling or prerequisite information (e.g., GhostRigger must be running, UE5 must be available), but for a complex orchestration tool it provides enough for an agent to invoke it correctly in most cases.

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 compensate. It explains each parameter's role, including the critical shared-folder constraint for export_path, the default for ue5_destination_path, and the conditional nature of skeleton (SkeletalMesh only). This is strong compensation for the bare schema.

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 a two-step pipeline: export via GhostRigger then import into UE5, with specific verbs and resources (export MDL to FBX, import FBX as StaticMesh/SkeletalMesh). It distinguishes itself from siblings like ghostrigger_export_model and import_static_mesh by combining both steps into one orchestrated operation.

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 provides clear step-by-step usage context and notes the shared/mounted folder requirement for export_path. It doesn't explicitly name alternative tools or when-not-to-use conditions, but the pipeline nature and KB reference give adequate context for an agent to know when to invoke it.

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