set_camera

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

Emphasizes that changes are runtime-only and lost on reload, which adds behavioral context beyond the annotations (destructiveHint, idempotentHint). No contradiction with annotations.

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 concise statements: one for purpose, one for usage requirement. No redundant information.

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?

Covers essential behavioral context (transient changes, user permission) and purpose, adequate for a parameter-rich tool with no 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?

Schema coverage is 100%, but the description adds value by grouping parameters (e.g., fov/aspect for PerspectiveCamera, left/right/top/bottom for OrthographicCamera) not present in the schema descriptions.

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?

Clearly states 'Modify camera' with specific parameters (position, rotation, FOV, etc.) and distinguishes from sibling tools like camera_details (read) and set_object_transform (for objects).

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?

Explicitly instructs to ask the user whether a runtime preview or persistent code change is desired, providing clear when-to-use guidance and differentiation from potential alternatives.

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