scene.camera.set

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

Annotations already indicate this is not read-only and is destructive/idempotent. The description adds meaningful transactional behavior: the active camera is changed and the previous camera is restored on rollback. It could further describe failure behavior around expected identity or generation, but the rollback semantics are a valuable addition 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?

The description is one sentence with no filler. The primary action is front-loaded and the rollback consequence is stated immediately, making it easy to scan and parse.

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?

The description is adequate for selecting the tool and understanding its transaction/rollback nature, especially with annotations and an output schema present. However, it leaves key invocation details undocumented, particularly how to obtain or satisfy the expected_camera_identity and expected_scene_generation, and what 'structural transaction' entails. This is a minimum-viable description with clear gaps.

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 must compensate, but it does not. It only hints at camera_name and transaction context; expected_camera_identity, expected_scene_generation, and idempotency_key remain unexplained. With five required parameters, this is a significant gap.

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 and resource: 'Set one exact Camera object as the active scene camera.' It also clearly distinguishes this from broader sibling operations like object.set or world.set by focusing on the scene camera and the exactness of the identity. The rollback behavior is stated without ambiguity.

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 description explicitly states the operation happens 'inside the structural transaction,' and clarifies what happens on rollback. It does not name alternatives or give exclusions, but the context is clear enough for an agent to know this is the tool for changing the active scene camera within a transaction.

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