cascadeur_set_camera

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

The annotations already indicate destructiveHint=true, but the description adds no context about what changes are made, whether the previous camera position is lost, or any side effects. It only clarifies the unit system ('scene units'), which is useful but insufficient for a destructive operation.

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 concise sentence with no redundant words. It front-loads the verb and resource, and every phrase ('active viewport', 'position/target', 'scene units') adds meaningful 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?

For a 2-parameter tool with no output schema and no parameter descriptions, the description is too sparse. It omits key context such as optionality semantics, the distinction between position and target, and any behavioral caveats from the destructive annotation.

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?

The schema has zero description coverage, leaving the meaning of 'position' vs 'target' and the null defaults unexplained. The description mentions both fields and scene units, but does not clarify how the two camera parameters relate (e.g., camera origin vs look-at point) or what passing null does.

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 names a specific verb ('Set'), a specific resource ('active viewport camera'), and the specific data being modified ('position/target') plus units. This clearly distinguishes it from sibling tools like cascadeur_get_camera and cascadeur_set_view_mode.

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 cascadeur_get_camera or cascadeur_set_view_mode. The description only states what it does, not when it is the appropriate choice or any prerequisites like requiring an active scene or viewport.

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