unreal_delete_actor

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

Adds significant context beyond annotations: it warns this is destructive, notes that recovery requires an undo which the server cannot trigger, and advises confirming the target. This covers consequences and mitigation, exceeding the basic destructiveHint.

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?

Well-structured with clear sections (warning, args, returns, examples). The critical warning is front-loaded, and every sentence serves a purpose without redundancy.

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 single-parameter destructive action, the description covers the action, consequences, usage rules, return format, and error handling. It is complete for an agent to call correctly without further assumptions.

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?

The description explains the 'actor' parameter as 'Label or path identifying the actor to destroy' and references using unreal_list_actors for confirmation. Though the schema already has a similar description, the tool description adds the safety context of verifying the target before destruction.

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 states a specific verb ('remove') and resource ('actor from the current level'), clearly distinguishing from siblings like unreal_list_actors (listing) and unreal_spawn_actor (creation). It is not a tautology and conveys a precise action.

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?

Explicitly provides when-to-use ('user explicitly asks to remove a placed object') and when-not-to-use ('only want to hide it, or when unsure which actor'), and directs the agent to unreal_list_actors for disambiguation. This is model guidance.

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