ue_detach_actor

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only states the basic operation of detaching and briefly explains the 'keep_world' parameter. It omits details on side effects (e.g., transform changes if keep_world is false), reversibility, permissions, or whether it is destructive.

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 extremely concise: one sentence for purpose and two bullet points for parameters. Every word adds value, and the purpose appears first. There is no wasted text.

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 tool with 2 parameters and no output schema, the description covers the basic semantics but lacks broader context like prerequisites (actor must have a parent), behavioral changes (what happens to transforms), or how it relates to sibling tools. It is minimally viable but incomplete.

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 'label' as the actor's label and 'keep_world' as preserving world position instead of relative position, with default true. This adds meaningful context beyond the schema's type and title, though it could clarify what 'relative' means.

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 explicitly states 'Detach an actor from its parent' (Italian: 'Sgancia un attore dal suo padre.'), which clearly identifies the action (detach) and the resource (actor from parent). This distinguishes it from sibling tools like ue_attach_actor (attach) and ue_delete_actor (delete).

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 no guidance on when to use this tool versus alternatives, such as when to detach vs. attach, or prerequisites like requiring an attached actor. No exclusions or context for usage are mentioned.

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