view

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds the behavior of each operation (zoom, screenshot) but does not disclose potential side effects, coordinate system details, or error conditions. It adds some behavioral context beyond the annotation but not deeply.

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 compact, front-loaded with the main purpose, and lists operations in a clear bullet-like format. Every sentence earns its place, with no redundant filler.

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?

Given the tool's moderate complexity (3 operations, 5 params, output schema present), the description is mostly complete. It covers the operation types and their arguments, and the output schema likely explains return values. It lacks finer details like coordinate units or default behavior, but remains sufficient for basic usage.

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 explain the 'operation' parameter values and mentions that zoom_window uses x1, y1, x2, y2, but does not clarify their meaning beyond being coordinates, nor the role of null defaults for optional parameters. Partial compensation for the schema gap.

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' with a specific verb and resource, and enumerates three distinct operations (zoom_extents, zoom_window, get_screenshot). It is easily distinguishable from sibling tools focused on layers, drawing entities, blocks, etc.

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 description implies usage via the operation list, but provides no explicit guidance on when to choose this tool over alternatives. It does not mention exclusions or context such as 'use this when you need to adjust the view or capture the screen' – the purpose is stated but not elaborated.

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