blender_create_camera

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

It discloses the core behavior of creating and activating a camera, and notes unit conventions, which adds some context beyond the sparse annotations. However, it does not describe side effects such as whether the active camera is changed, how existing cameras are affected, or what happens if a camera with the same name exists.

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, efficient sentence with the primary action front-loaded. It packs the key unit information without wasted words or redundancy.

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 six-parameter mutation tool with no output schema and minimal annotations, the description is only partially complete. It covers units and look_at behavior but omits the meaning of the active and collection parameters and the exact activation side effect, leaving an agent to guess important execution details.

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?

With schema description coverage at only 33%, the description partially compensates by stating that location is in meters, focal_length is in millimeters, and look_at accepts a target point or object name. But it repeats schema information for location/look_at and leaves name, active, and collection semantically unexplained.

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 opens with 'Create and activate a camera,' a specific verb and resource that clearly identifies the tool's action and object. This distinguishes it from sibling tools like blender_create_primitive and blender_set_point_light, and the extra unit details reinforce its domain.

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 implies when to use the tool—when a camera needs to be created and activated—but gives no explicit context, exclusions, or comparison with alternatives. It does not state, for example, when to choose this over configuring an existing camera or placing a light.

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