Add a camera to a Blender scene with a specific focal length, name, and location for rendering or animation.
Create a camera with specified focal length.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| location | No | ||
| focal_length | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0+hardened.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It only states the creation action, leaving unclear whether the camera is added to the active scene, whether it becomes the active camera, what naming behavior occurs, or what units focal_length uses.
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?
A single, front-loaded sentence with no filler. Every word contributes meaning, and the key customization, focal length, is stated immediately after the action.
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 low-complexity creation tool with fully optional parameters and an output schema, an agent can likely invoke this successfully. However, the description leaves parameter semantics, side effects, and usage-versus-alternatives unaddressed, so it is only minimally complete.
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 0%, so the description must compensate for parameter meaning. It mentions focal_length but adds no detail about units, range, or default behavior, and it entirely omits the name and location parameters. The schema defaults help, but the description does not fill the gap.
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 names the specific operation (create), the resource (camera), and the key attribute (focal length). This clearly separates it from sibling tools like list_cameras, set_camera_property, and set_active_camera, which are not creation actions.
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 no guidance on when to use this tool versus alternatives such as set_camera_property or set_active_camera, and no context about prerequisites like requiring an active scene. Usage is only implied by the word 'create'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.