blender_set_active_camera

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

Annotations already flag the operation as non-read-only and non-destructive, and the description adds meaningful behavioral context: it changes state and must precede render/capture operations. It doesn't discuss return values or error behavior, but the annotations reduce the burden.

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?

Two short sentences, with the core purpose front-loaded and the usage condition immediately after. No filler or redundant information.

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-required-parameter setter, the description covers the effect and the exact call context. It doesn't mention error handling or return values, but those are not critical given the tool's simplicity and the annotations.

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 required 'name' parameter has no schema description, and the description only implies that it refers to a camera by saying 'which camera.' It doesn't specify whether the value is the camera object name or data name, or how to list valid cameras. The response_format parameter is already documented in 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 clearly states the tool's purpose with a specific verb and resource: 'Choose which camera the render uses.' It is distinguishable from related siblings like blender_add_camera or blender_set_context, though it doesn't explicitly name them as alternatives.

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 gives explicit, actionable usage guidance: 'Call this before blender_render or blender_capture_viewport with mode='camera' if the scene has several.' It lacks an explicit when-not-to-use statement or named alternative tools, but the conditional is clear enough.

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