foundry_delete_scene

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

The description adds no behavioral context beyond what the annotations already provide (destructiveHint=true). It does not mention whether deletion is permanent, cascades to related documents, requires specific permissions, or returns a confirmation.

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 a single, clear sentence that immediately states the action and supported identifier types. Every word contributes meaning, with no filler or repetition.

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?

Despite being a destructive operation, the description lacks essential context: it does not state that at least one of name/sceneId is required, what happens if both are given, or what the tool returns after deletion. Given the 4-parameter schema with no required fields and no output schema, this is insufficient for an agent to invoke the tool correctly.

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 description clarifies that 'name' and 'sceneId' are alternative identifiers for the scene, adding some meaning to those parameters. However, schema coverage is 50% (only userId and clientId have descriptions), and the description does not compensate by explaining whether both identifiers can be used together or which one is preferred.

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 a specific verb ('Delete') and resource ('scene'), and clearly states the identification methods ('by ID or name'). This distinguishes it from sibling tools like foundry_update_scene or foundry_delete_entity.

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?

There is no guidance on when to use this tool versus alternatives, nor does it mention that a scene identifier must be provided (name or sceneId) despite no required parameters in the schema. It does not clarify whether name or sceneId takes precedence if both are supplied.

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