foundry_delete_entity

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

Annotations already declare destructiveHint=true, so the destructive nature is covered. The description adds that selection can be based on UUID or current selection, which is useful targeting context. However, it does not disclose consequences like irreversibility, cascading deletes, or permission requirements, so it adds limited value beyond annotations.

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?

A single, direct sentence with no filler. The verb, resource, and targeting method are front-loaded, making it easy to scan.

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?

With zero required parameters, the description does not explain how the tool determines its target if neither uuid nor selected is provided. It also omits return values, error behavior, and any interaction with the Foundry client context, leaving a simple but ambiguous operation under-specified.

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 coverage is 50% (uuid and selected lack descriptions). The description partially compensates by explaining the two targeting modes, but it does not clarify the relationship between uuid and selected (e.g., precedence if both are set) or expand on userId/clientId, which already have 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?

The description clearly states the action ('Delete'), the resource ('Foundry entity'), and the two targeting modes ('by UUID or the current selection'). This distinguishes it from sibling tools like foundry_get_entity, foundry_update_entity, and specific delete tools for folders/scenes.

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 on when to use this tool versus alternative delete tools (e.g., foundry_delete_folder, foundry_delete_scene) or when to prefer UUID over selection. There are also no prerequisites or exclusions mentioned.

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