foundry_update_scene

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

The annotation readOnlyHint: false already indicates a write operation, but the description adds no further behavioral context. It does not mention side effects, required permissions, or whether existing data is overwritten. No contradiction with annotations exists, but the description falls short of disclosing important traits.

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 sentence, but it sacrifices clarity for brevity. The phrasing 'by ID, name, or active status' is confusing and omits critical details, making it under-specified rather than appropriately concise.

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 6 parameters, a required nested object, no output schema, and minimal annotations, the description is insufficient. It does not explain how the tool behaves, what the response looks like, or how to structure the data parameter, leaving significant gaps for an agent.

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% (data, userId, clientId have descriptions; name, active, sceneId do not). The description hints that name and active are relevant, but it fails to explain the required 'data' parameter and the role of sceneId. The ambiguous 'by ID, name, or active status' offers minimal value beyond the schema.

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 states the core action 'Update a scene', which identifies the tool as a mutation operation on scenes, distinguishing it from siblings like create or delete. However, the phrase 'by ID, name, or active status' is ambiguous—it could mean selection criteria or fields to update—leaving the exact purpose unclear.

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 provided on when to use this tool versus alternatives such as foundry_create_scene, foundry_switch_scene, or foundry_delete_scene. The description neither states prerequisites nor mentions any exclusions or fallback tools.

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