create_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 mentions aiming behavior but does not state side effects such as the camera becoming active by default, collection placement, or what happens to any existing camera. This is a meaningful gap for a creation tool.

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, front-loaded with the core purpose and followed by a targeted usage note about aiming. Every sentence earns its place and there is no redundant or filler 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?

The description is adequate for basic camera creation and aiming, but it omits context around important defaults and side effects, such as set_active defaulting to true and making the camera the render camera. Given 13 optional parameters and no output schema or annotations, a bit more contextual guidance would improve 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 54%, so the description is not required to fully compensate, and it does add useful context for look_at and look_at_object by explaining their role in pointing the camera. However, it adds no meaning for the many other parameters such as clip_start, clip_end, collection, or ortho_scale.

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 a specific verb and resource: 'Create a camera.' It also distinguishes itself from the related sibling frame_objects_with_camera by explaining that camera aiming can be done here or via that alternative, which also computes distance.

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 clear guidance for aiming: pass look_at/look_at_object for pointing, or choose frame_objects_with_camera when distance should be computed. It does not cover exclusions for other siblings like look_at or set_camera_transform, but the context for this tool is clearly stated.

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