setCameraProperties

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

No annotations are provided, so the description carries the full behavioral burden. It implies mutation and requires an existing camera, but says nothing about partial-update semantics (whether omitted properties are left untouched or reset), undo/reversibility, permission requirements, or how errors surface when the named camera is missing.

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 sentence with the verb and target front-loaded, which is efficient. The long trailing enumeration of property names repeats what the schema already lists, so it is slightly overlong rather than perfectly tight.

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 20-parameter mutation tool with no annotations and no output schema, the description covers the transform/optical properties but is silent on how the target camera is addressed (cameraName/cameraIndex/compName), on cameraType switching, and on the fact that all parameters are optional and independently applied.

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 100%, so all 20 parameters are already documented at the field level; baseline 3 applies. The parenthetical list largely restates schema properties and omits the selection-related parameters (cameraName, cameraIndex, compName) and cameraType, so it adds little meaning beyond the schema.

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 a specific verb ('set or modify'), a specific resource ('3D camera layer'), and enumerates the property families affected. The word 'existing' distinguishes it from createCamera and createCameraRig, though it does not explicitly distinguish it from applyCameraMove or setLayerProperties.

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?

Usage is only implied: the tool operates on an 'existing' camera layer, so a camera must already exist. There is no statement of when to prefer this over applyCameraMove, trackCameraToLayer, or the generic setLayerProperties, and no prerequisite or exclusion guidance.

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