blender_camera

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

Annotations are all false (readOnlyHint=false, destructiveHint=false, etc.), so the description itself must disclose behavioral traits. It only lists operations without explaining side effects, such as modifying the current scene, creating new objects, or affecting the active camera state. For example, 'Create a new camera' does not state that it adds a camera to the scene or require existing context.

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 concise, front-loaded with the core purpose, and uses a bulleted list for operations. Every sentence contributes useful information, and there is no redundant text.

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?

An output schema exists, so return values are adequately documented elsewhere. However, the description lacks guidance on which parameters apply to each operation, which is important given 10 parameters and 3 operations. For instance, it doesn't explain that camera_name is needed for set_active_camera. This is a clear gap in completeness.

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 description coverage is 100%, so baseline is 3. The description adds some value by implying which parameters are relevant for each operation (e.g., set_camera_lens uses lens and sensor_width), but it does not clarify which parameters are required per operation. The parameter descriptions in the schema already cover individual meanings.

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 ('Create and control cameras in Blender scenes') and enumerates three distinct operations via the operation parameter. This differentiates it from siblings like blender_scene or blender_lighting, which target other aspects of Blender.

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 provides clear usage context by explaining that multiple operations are supported and listing them. While it does not explicitly name alternatives or exclusions, the camera-specific focus makes it evident when to use this tool. However, it could be improved by contrasting with other scene tools.

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