maya_unreal_prepare

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

With no annotations provided, the description carries full responsibility. It discloses the single undo unit, the negative-scale caveat (only warns, doesn't fix), the dry_run behavior (no scene mutation), and the selection fallback logic. This is comprehensive behavioral disclosure for a mutation tool.

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 information-dense yet compact: a one-line summary, a usage note, a caveat, and a parameter list. It is front-loaded with the main purpose and contains no filler sentences.

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?

For a 7-parameter tool with no annotations and no output schema, the description covers purpose, workflow, behavioral edge cases, and all parameter semantics. An agent has sufficient information to decide when to call it and how to set each argument.

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 fully document parameters. It defines all 7 parameters with clear meaning, enumerates pivot options with concrete definitions ('center', 'base', 'origin', 'keep'), and provides practical guidance on choosing between 'base' and 'origin'. This exceeds what the schema alone offers.

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 the tool's function: 'Performs pre-export cleanup in one go (freeze, history, pivot, naming).' This specific verb and resource list distinguish it from sibling tools like maya_unreal_check (diagnostic) and maya_unreal_cleanup_materials (material-specific).

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 explicitly instructs to first check status with maya_unreal_check, establishing a workflow ordering. It also explains the undo-unit behavior, which informs safe usage. However, it does not explicitly exclude or compare against alternative sibling tools, so the when-not-to-use guidance is somewhat implicit.

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