Set view mode and camera angle

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

No annotations are provided, so the description carries the full behavioral burden. It never says whether these changes are viewport-only (non-destructive, unsaved) or persist into the project, whether 'move the camera' affects the scene camera or just the view, or whether the action is undoable — all material for a no-annotation mutation tool.

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 core capability and its enumerated values are front-loaded in the first sentence, with the workflow hint trailing as a short second sentence. The inline value lists are dense but every token carries information; no filler sentences are present.

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?

There is no output schema, so the description needn't cover return values, and the enumerated inputs are complete. It is still thin on the call itself: with all three parameters optional it never states what happens when they are omitted, nor whether the call returns confirmation, leaving an agent guessing about defaults.

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 only 33% (just 'zoom'), so the description must compensate, and it does: it enumerates every legal value for both `angle` and `view_mode`, which the schema leaves as bare strings. It adds nothing beyond the schema for `zoom`, and does not note accepted casing or whether values are case-sensitive, so it stops short of a 5.

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 (change) and a concrete resource (viewport view mode + preset camera angle), and enumerates the exact accepted values for both, which is well beyond a tautology. It does not, however, distinguish itself from the nearby sibling bb_set_mode, whose name invites confusion with 'view mode' — an agent must infer the difference.

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?

'Useful before bb_screenshot' gives one genuine contextual cue for when to reach for this tool. There are no exclusions, no statement of alternatives (e.g., when to use bb_set_mode instead), and 'useful' is a soft rather than directive recommendation, so usage remains implied rather than explicit.

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