world.set

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

Annotations already declare this as non-read-only, idempotent, and destructive, and the description does not contradict them. The description adds useful transaction-scoping behavior, but does not explain destructive consequences, concurrency expectations, or failure modes beyond the schema's expected_* fields.

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, front-loaded sentence with no filler. It efficiently communicates the core action, target resources, and transaction requirement, though it is slightly compressed given the complexity of the tool.

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 12 parameters, zero schema descriptions, and a transaction-based API, the description is incomplete. It omits how expected_* fields work, what 'exact local environment image' means, and how the transaction lifecycle constrains invocation. The presence of an output schema helps with return values but not with input semantics.

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 had to compensate for explaining 12 parameters. It only gestures at 'World background' and 'environment image', while required fields like transaction_id, expected_scene_generation, idempotency_key, and the expected_* optimistic concurrency fields remain unexplained.

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 a clear action ('Create or modify') on a distinguishable resource ('current World background' and 'optional exact local environment image'). This is enough to set the tool apart from generic object/scene tools like object.set or scene.camera.set. However, 'exact local environment image' is domain-specific and not fully explained.

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?

The phrase 'inside the active structural transaction' gives an explicit context constraint: this must be called within a transaction lifecycle, likely between begin and commit/rollback. It does not state exclusions, when not to use it, or which sibling tools would be better for related but different operations.

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