delete_entity

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It identifies the operation as deletion but does not disclose whether deletion is permanent, undoable via the sibling undo tool, or what happens to child entities or attached components.

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 text is short and front-loaded with the core operation. The Args section is redundant with the input schema but harmless, and there is no irrelevant prose.

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 one-parameter tool with an output schema, the essential invocation information is present: delete the entity named by entity_id in the current level. However, the lack of any destructive-behavior caveat or ID source note leaves the definition only 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 should add meaning beyond the field name. 'The entity ID to delete' essentially restates the schema's 'Entity Id' title and does not specify the ID format, how to obtain valid IDs, or whether the ID is a UUID, name, or editor identifier.

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 uses the specific verb 'Delete' with the entity resource and scopes it to 'the current O3DE level.' That wording is enough to separate it from sibling tools like create_entity, duplicate_entity, and remove_component, which target different operations or a different granularity.

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 is given for when to invoke this tool instead of alternatives, and no prerequisites are stated. For example, it does not mention that list_entities can supply valid entity IDs or that remove_component is the choice for deleting a component rather than the whole entity.

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