set_active_camera

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

No annotations are provided. The description implies a mutation (changing active camera) but does not disclose side effects, error behavior if the camera name is missing or invalid, or any other consequences. The phrase 'to an existing camera object' is a precondition but not behavioral detail.

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 very short, but the parameter listing duplicates schema information. It is front-loaded with the main action, but the param section could be omitted or integrated more efficiently. Still, no extraneous 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?

For a single-parameter, no-output-schema tool with no annotations, the description lacks completeness. It does not explain what happens if the camera name does not exist, whether the active camera is changed immediately, or any return value. More context would be beneficial for an agent.

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 coverage is 0% (the schema has no description for the 'name' property). The description adds 'Camera object name' which is minimal and largely redundant with the property name. It provides no additional meaning beyond what is obvious from the 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 explicitly states the tool's purpose: 'Set the active render camera to an existing camera object.' It uses a specific verb ('set') and resource ('active render camera'), clearly distinguishing it from siblings like 'create_camera' or 'render_from_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?

No guidance on when to use this tool versus alternatives. Siblings such as 'render_from_camera' also involve cameras but without setting active. The description does not mention prerequisites or exclusions.

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