set_viewport_camera

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about what happens when pane_name is omitted, whether a nonexistent camera_path errors, whether the view change is undoable, or whether it affects only the active pane. 'Set' implies mutation but the scope and failure behavior are undisclosed.

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 filler or redundancy. It is efficient, though the brevity comes at the cost of the missing details noted elsewhere rather than being a model of compact completeness.

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 state-changing viewport tool with zero annotation coverage, 0% parameter documentation, and no output schema, the definition is too thin. An agent cannot determine pane targeting rules, camera path syntax, or error conditions from this one sentence.

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% for two parameters. The phrase 'specific camera' gestures at camera_path but gives no format guidance (node path? string name?), and the optional pane_name parameter is not mentioned at all, nor is its default-to-active-pane behavior explained. The description adds almost nothing over the bare schema.

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 states a specific verb and resource ('Set the viewport to look through a specific camera'), which is concrete enough for an agent to distinguish it from direction/renderer/display-setting siblings. It does not, however, explicitly name any sibling or contrast itself with them, keeping it below 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 when-to-use guidance, no mention of prerequisites (e.g., the camera node must exist), and no reference to alternatives such as set_viewport_direction or set_viewport_renderer. The agent must infer the usage context entirely from the tool name.

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