ue_detach_actor

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

No annotations are provided, so the description is the sole source. It mentions the detach action and keep_world behavior, but lacks details on edge cases (e.g., invalid label, actor without parent) or side effects. Insufficient 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 extremely concise, using a single line for the purpose and two lines for parameters. No redundant information; front-loaded with the core action.

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?

Given the simple tool (2 params, no output schema), the description covers the essential purpose and parameter meanings. However, it omits common usage contexts like error handling, prerequisites (actor must have a parent), and return value (success/failure). It is minimally complete.

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 add value. It does so by explaining both parameters: 'label' is the actor's label, and 'keep_world' maintains world position. This clarifies the boolean's behavior beyond the schema's title.

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 'Sgancia un attore dal suo padre' (detaches an actor from its parent), which is a specific verb and resource. It is distinct from siblings like ue_attach_actor, but does not explicitly differentiate itself.

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 implies usage for detaching actors from parents but provides no explicit guidance on when to use it versus alternatives, prerequisites, or the implication of keep_world parameter. It assumes the actor already has a parent.

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