execute_unreal_handoff

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

Annotations already declare the non-read-only, non-destructive, closed-world profile, and the description adds real context beyond them: prerequisites (engine registration, loopback remote execution), a safety constraint (executes only the bundled handoff script), and idempotency (a completed matching receipt is reused). It stops short of describing failure modes or what verification actually checks.

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?

Three short sentences, each earning its place: purpose first, prerequisites second, safety/idempotency constraints last. No filler or restatement of the tool name.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a mutation tool with five undocumented parameters, the description omits what happens on retry (attempt vs. reused receipt), what the verification step validates, and how a partial failure is reported.

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% and the description never mentions job_id, target, attempt, source_kind, or sample_index. The nested UnrealTarget type carries its own description and the asset_name pattern/enum are self-documenting, but the retry-shaped parameters (attempt, sample_index) and their relationship to receipt reuse are left completely unexplained.

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?

States a specific verb (import) and resource (a prepared animation into an open Unreal project) plus a verification step, so the agent knows this is the execution stage of a handoff. It implicitly separates itself from prepare_unreal_handoff and get_unreal_report, but never names those siblings explicitly.

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?

"Requires the operator's engine registration and loopback Python remote execution" and "its exact open Unreal project" spell out concrete preconditions an agent must confirm before calling. It does not state when to prefer this over prepare_unreal_handoff or what to do on failure, so no explicit exclusions are given.

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