set_editor_camera

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

With no annotations, the description discloses important behavioral traits: the camera moves in world space and look_at is applied after rotation_degrees and overrides it. This goes beyond basic 'move' by explaining parameter interaction, though it omits fov behavior and potential defaults.

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 well-structured sentence with a semicolon separating the main action from a crucial caveat. It is front-loaded and contains no extraneous words.

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 4 parameters, no annotations, and no output schema, the description covers the core operation and the key interaction between look_at and rotation. However, it leaves gaps around fov semantics, default behavior, and return values, making it minimally viable rather than comprehensive.

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 adds semantic meaning for look_at and rotation_degrees (ordering and override) and implies position via 'move', but fov is not explained at all. Parameter names and nested structures are in the schema, providing some baseline understanding.

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 states the tool moves the 3D editor viewport camera in world space, which is a specific verb + resource. It distinguishes itself from siblings like get_editor_camera and setup_camera_3d by explicitly mentioning viewport camera movement.

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?

Provides useful context about operating in world space and the ordering of look_at vs rotation_degrees, which helps in usage. However, it does not explicitly mention alternatives or conditions when to use this tool instead of get_editor_camera or setup_camera_3d.

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