camera_set

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the mutation and open-world profile is covered. The description adds the 'fixed camera' framing and the REGION coordinate system, but does not say it replaces/overrides the current view state or interact with camera_release, which is the main behavioral gap.

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?

Two tight sentences with the action and coordinate frame front-loaded and no filler. The second sentence is advisory rather than redundant, so it earns its place, though it is slightly tangential to invocation.

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 two-parameter tool with annotations present and no output schema, the safety and coordinate-frame context is adequate. However, with 0% parameter coverage and no return/blocking behavior described, an agent still lacks enough to construct valid position/focus values confidently.

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% for two required array parameters, so the description carries the whole burden. It supplies only the coordinate frame ('REGION coordinates'); it never explains that position/focus are numeric arrays, their expected length/order (e.g., x,y,z), or units, leaving the parameters effectively unexplained.

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?

States a specific verb ('Set') and resource ('a fixed camera and focus') plus the coordinate frame (REGION coordinates), which separates it from camera_release and the preview tools. It is clear, though it never names a sibling to differentiate against.

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?

'Viewport capture is needed to verify composition' implies the follow-up workflow (set the camera, then capture), which is useful implied context. There is no explicit when-to-use/when-not guidance relative to siblings like camera_release, capture_orbit, or mesh_preview_camera.

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