set_viewer_context

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

No annotations are supplied, so the description carries the full disclosure burden and delivers little. It does not say whether the pane must already exist, what happens with an invalid network path, whether this also changes the selected current network, or whether the change is reversible. For a state-mutating viewer tool, 'point at' is not enough behavioral context.

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?

One short sentence, front-loaded with the action and resource, with zero filler. It is arguably too terse for a three-parameter tool, but nothing in it is wasted.

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?

With no annotations, 0% schema coverage, and no output schema, the description is the only explanatory source and it covers roughly two of three parameters in passing while saying nothing about effects or failure modes. It is insufficient for the complexity of a viewer-state mutation.

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% across three parameters, so the description must compensate and only partly does. It implies the network path and optional node (current_node), but pane_name is never mentioned, leaving an agent to guess that multi-pane targeting exists and how it interacts with the network choice.

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 and target: point the Scene Viewer at a network, with an optional node. That is more concrete than the tool name alone, since 'viewer context' is otherwise abstract. It does not, however, distinguish this from closely related siblings like set_current_network or set_viewport_camera, so an agent must guess which 'set' to use.

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 prerequisites, and no named alternative. Given a sibling set packed with set_current_network, set_viewport_* and set_current_take, the absence of any steering is a real gap.

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