set_active_camera

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

The idempotentHint annotation already covers the main non-obvious behavioral trait. The description adds no further behavioral context, such as whether the camera must exist or what happens on failure. It does not contradict the annotation.

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 short, front-loaded sentence with no wasted words. It is fully appropriate for the simplicity 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?

For a simple one-parameter tool, the description is minimally acceptable, especially with the idempotent annotation and output schema available. However, it lacks parameter semantics and usage differentiation from sibling tools, so it is not fully complete.

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 schema only defines 'name' as a required string with no description, and the description does not explicitly clarify that this is the camera name. Although it is inferable from the tool name, the description adds little meaning beyond the raw 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 'Set the active scene camera.' uses a specific verb and resource, clearly distinguishing this from sibling tools like set_viewport_camera or list_cameras. It succinctly states exactly what the tool does.

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 implies the tool should be used when you need to change the active scene camera, but it provides no explicit guidance on when to use it versus alternatives like set_viewport_camera. It gives no exclusions or prerequisites.

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