set_active_camera

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

The description adds little beyond the tool name; it only adds 'scene' to indicate scope. With idempotentHint already provided, the description does not disclose additional behavioral implications such as effects on rendering or any side effects of changing the active camera.

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, concise sentence with no filler. It is front-loaded and efficient, though its brevity comes at the cost of necessary explanatory content.

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?

Even for a simple one-parameter tool, the description is incomplete: it does not clarify the expected input, differentiate from set_viewport_camera, or mention that it affects the scene/render. The presence of an output schema does not compensate for the missing usage context.

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 has one parameter 'name' with zero description coverage, and the tool description does not explain what 'name' refers to. The agent is left to guess it is a camera name, which is not explicitly stated.

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 specific action: set the active scene camera. It is clear and the qualifier 'scene' narrows the resource, but it does not explicitly differentiate from similar siblings like set_viewport_camera.

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 such as set_viewport_camera or set_camera_property. The agent must infer usage solely from the name, which is insufficient given the many camera-related siblings.

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