set_camera_lens

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It merely says 'configure' without specifying whether changes apply immediately, whether omitted parameters are reset, if the camera must exist prior, or what errors may occur. This is insufficient for a mutation 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?

The description is a single sentence with no wasted words, which is concise. However, it is so brief that it omits crucial details. Conciseness is appropriate, but the structure lacks the explanatory depth needed for a tool with 12 parameters.

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 complex tool with 12 parameters, no annotations, and no output schema details (though one exists), the description is incomplete. It does not explain the purpose of each parameter group, how they work together, or what the tool returns. An agent would have difficulty invoking it correctly with only this description.

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. It mentions categories (lens, clipping, shift, sensor, DOF) but maps none of the 12 parameters to these categories. It does not explain units, ranges, defaults, or interactions between parameters (e.g., DOF focus object vs distance). The value added over the schema is minimal.

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 states a specific verb ('Configure') and a clear resource ('a camera') with the categories of settings (lens, clipping, shift, sensor, DOF). This distinguishes it from create_camera and set_active_camera, though it doesn't explicitly mention the required camera_name parameter, which the schema does.

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?

There is no guidance on when to use this tool versus alternatives like create_camera or set_active_camera. It doesn't mention that a camera must already exist, whether this modifies an existing camera, or any prerequisites. The context for use is only implied.

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