spatial_bind_generated_assets_to_composition

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states the key behavior: it returns dry-run placement, validation, and iteration handoffs 'without mutating the Unreal Editor scene.' This covers the most important safety trait, though it does not discuss error cases or input format edge cases.

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 compact and well-structured: a one-line purpose, a KB pointer, a focused functional paragraph, and a representative call example. Every sentence adds useful information with no filler.

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 provides purpose, inputs, non-mutation guarantees, and result handoffs, and an output schema exists. However, with zero schema description coverage and several optional parameters whose semantics are unclear, an agent would still have to infer how clearance_padding, surface_tolerance, and include_unresolved_steps affect the binding operation.

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 helps by explaining the roles of composition_plan_json, import_results_json, and asset_overrides_json, but it leaves clearance_padding, surface_tolerance, and include_unresolved_steps entirely unexplained beyond their names and defaults.

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 first sentence states a specific verb and resource: binding imported/generated assets back into a spatial composition plan. The body adds scope by naming the consumed inputs and explicitly clarifying that this is a dry-run planner that does not mutate the scene, which helps distinguish it from applying or placement siblings.

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 clearly identifies when this tool is relevant: when a spatial composition plan exists and Tripo import results or manual asset overrides are ready to be bound into it. It does not name sibling alternatives or state when-not-to-use, but the dry-run/handoff language gives a clear workflow context.

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