nbc_view

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

The description discloses the core behavior: zoom operations and screenshot capture, including the caveat that screenshots are canvas-only if available. However, with no readOnly/destructive annotations present, the description carries the burden and still omits context such as possible side effects on the viewport or output behavior.

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 dense sentence with no filler. The main action is front-loaded and every phrase contributes meaning.

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 relatively simple view tool with an output schema, the description gives the essential operation modes and screenshot option. However, the required operation parameter's allowed values are not formally specified, and the data parameter is left entirely unexplained, so an agent may still need to guess or inspect external context.

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 compensate. It does add some meaning by suggesting operation values like zoom_extents and zoom_window, but it never explicitly maps those to the operation parameter, nor does it explain the data parameter at all. The screenshot behavior is only loosely tied to include_screenshot.

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 clearly identifies the tool as a view operation and specifies the concrete actions: zoom_extents/zoom_window plus screenshot. It is distinct from the domain-specific siblings like nbc_wall or nbc_layer, though it does not explicitly name an alternative.

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?

No guidance is given about when to use this tool versus any alternative. The intended use is only implied by the word 'View' and the sibling tool names, with no exclusions or conditions stated.

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