set_camera_transform

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it only states the high-level effect. It does not disclose whether omitted parameters remain unchanged, whether the operation mutates the scene, what return value is produced, or any side effects like invalidating view state.

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 one short sentence with no filler or redundancy, and it front-loads the core purpose. It is concise, though perhaps too concise given the tool's complexity.

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 tool with 10 optional parameters, no annotations, and no output schema, this description is insufficient. It lacks usage context, behavior details, and enough parameter explanation for an agent to reliably invoke the tool for non-trivial camera setup.

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 only 40%, so the description should compensate, but it adds almost nothing about parameter meaning. It mentions 'lens' generically but does not explain fov, clip planes, ortho_scale, look_at_object, or the interplay between location, rotation, and look_at.

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+resource ('Move a camera and adjust its lens') and clearly identifies the tool as a combined transform/lens operation. It does not explicitly distinguish itself from sibling tools like set_transform or look_at, but the camera-specific wording is enough for basic identification.

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 such as set_transform, look_at, or set_active_camera. It does not mention prerequisites, exclusions, or the active-camera fallback beyond the schema's brief 'Omit for the active camera' note.

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