camera_set

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description never explains what is destructive about moving a camera — whether the previous camera pose is lost, whether it is undoable, or whether it affects the saved scene/other users. With both parameters optional, it is also silent on what happens when neither is supplied, which is the most important behavioral detail for a zero-required-arg mutation.

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 front-loaded sentence with no wasted words; the core action and resource come first. It is arguably too terse for a destructive mutation, but there is no filler or redundancy.

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 destructive, zero-required-parameter mutation with no output schema and no parameter documentation in the schema, the description should explain the effect of calling with zero, one, or both arguments. None of that is covered, leaving an agent unable to predict the outcome of a call safely.

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 carry the burden; it does clarify that position and target are expressed in scene units and that the two are independent ('position or target'). However, it does not say whether both may be provided together, whether omitting one leaves it unchanged, or what the three-element array axes represent.

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 gives a specific verb ('Set') and resource ('active viewport camera position or target') and adds the unit of measurement ('scene units'), so the action is unambiguous. It does not differentiate itself from the closely related siblings camera_get and camera_frame, which is the only thing keeping it from a 5.

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 call this versus camera_get (read the camera) or camera_frame (presumably frame a subject), and no prerequisites or exclusions are stated. The agent must infer usage from the sibling names alone.

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