set_camera_property

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

With only idempotentHint: true in annotations, the description is the primary source for behavioral context, but it only lists parameter names and does not disclose effects like units, valid ranges, side effects, error conditions, or any dependency between properties. The idempotent annotation is not contradicted, but the description adds little beyond what is already known.

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 compact sentence with no wasted words. It front-loads the action and lists the settable properties clearly, making it easy to scan and understand.

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?

Given the 0% schema coverage and lack of annotations beyond idempotency, the description does not provide enough context for an agent to correctly set values. Missing units, ranges, and value-type associations make it insufficient for confident invocation, despite the presence of an output schema.

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?

The schema has 0% coverage for parameter descriptions, so the description must compensate. It does enumerate valid values for the 'property' parameter, which is valuable, but it does not explain value types per property (e.g., which properties expect numbers vs booleans) nor the meaning of the 'name' parameter. This partial compensation justifies a middle score.

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 identifies the action ('Set camera property') and enumerates the specific properties that can be set (focal_length, sensor_width, etc.), distinguishing it from other property-setting tools like set_material_property and set_light_property.

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 setup_camera_dof or set_active_camera. It does not mention exclusions, prerequisites, or preferability, leaving the agent to infer usage from the generic 'Set camera property' phrasing.

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