ue_delete_actor

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

No annotations are provided, and the description is too brief. It does not disclose side effects (e.g., permanent deletion, undoability), required permissions, or behaviors like whether it fails silently or throws errors. The tool performs a mutation but no behavioral details are given.

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?

One efficient sentence with no wasted words, but too brief for the needed information. It is well-structured but under-specified.

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 deletion tool with one parameter and no output schema, it lacks critical context: how to identify the actor (label meaning), uniqueness, behavior on missing label, and whether the level must be active. Incomplete for confident invocation.

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 single parameter 'label' has no description in the schema (0% coverage). The tool description only says 'with the given label', adding no additional meaning (e.g., what constitutes a label, whether case-sensitive, if it refers to actor name or tag). Does not compensate for missing schema descriptions.

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?

Description clearly states 'Delete from the current level the actor with the given label.' It specifies the action (delete), resource (actor), scope (current level), and identifier (label). This distinguishes it from siblings like ue_list_actors and ue_spawn_actor.

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?

No guidance provided on when to use this tool versus alternatives, prerequisites (e.g., level must be open, actor must exist), or what happens if the label is not found.

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