view

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

The annotations already declare readOnlyHint=true, covering the safety profile. The description adds operational detail but does not disclose potential side effects like modifying the current view state or any screenshot output details. Since annotations lower the burden, a score of 3 is appropriate.

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 concise and well-structured, front-loaded with a summary sentence followed by a clean bullet-style list of operations. Every line earns its place with no redundancy or fluff.

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 simple view-control tool, the description covers all operations and parameter context, while annotations provide the read-only safety hint and an output schema exists. It is complete enough for an agent to select and invoke the tool correctly without further explanation.

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 0%, but the description compensates by explaining x1, y1, x2, y2 in the zoom_window line and listing valid operations. This adds meaning beyond the bare schema types, clarifying when parameters apply, even though it stops short of detailing units or optional behavior.

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 states 'Viewport control and screenshot capture' and enumerates three concrete operations (zoom_extents, zoom_window, get_screenshot). This specific verb+resource phrasing distinguishes it well from sibling tools like drawing, entity, and layer.

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?

The operation list implies when to use the tool (zoom or screenshot), providing clear context. It does not explicitly name alternatives or exclusions, but the operations themselves are self-explanatory, making usage reasonably obvious.

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