set_active_camera

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says it sets the active camera, but does not mention side effects (e.g., whether it affects the viewport, what happens if the named camera does not exist, or whether the operation is reversible). This is a mutation but lacks any behavioral context beyond the action itself.

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 with no extraneous words; it is efficient and front-loaded with the action. However, it is so terse that it sacrifices necessary detail, which is a trade-off. Still, as far as concise writing goes, it earns a high score for being succinct and clear in structure.

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?

Given the tool has one parameter, no annotations, but does have an output schema (not shown), the description should at least clarify the expected parameter format and any preconditions. It does neither. The lack of any usage context or error-handling details makes it incomplete for reliable invocation.

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 zero description coverage for the only parameter, camera_name. The description does not compensate by explaining what camera_name should contain (e.g., an existing camera's name, a string identifier). It adds no meaning beyond the parameter name, leaving the agent without information about valid values or requirements.

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 verb ('set') and resource ('camera') and indicates the intention to make it 'active' in the scene. It is clear enough to differentiate from sibling tools like create_camera or list_cameras, though it does not explicitly name them. The phrase 'active scene camera' adds context about the effect, which is helpful.

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 creating a camera, adjusting lens properties, or listing cameras. There is no mention of prerequisites (e.g., the camera must exist), nor any exclusions or conditions for use. The description only states what it does, not when to invoke it.

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