zoom_window

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

With no annotations, the description is the sole source of behavioral information. It only says 'Zoom to a rectangular window' without disclosing side effects, coordinate system, or that it is a view-only operation. The tool name implies view manipulation, but this is not explicit.

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 single-sentence description is concise and front-loaded, saying exactly what the tool does without wasted words. While it lacks detail, the brevity is appropriate for a simple operation.

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?

Despite an output schema being present, the description is minimal. It does not explain the relationship to the drawing view, whether the zoom is persistent, or how the rectangular window is interpreted. For a 4-parameter tool, this feels incomplete.

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?

The schema lists four coordinate parameters with no descriptions, and the description does not clarify how x1,y1,x2,y2 map to the rectangular window (e.g., opposite corners) or the coordinate system. The parameter names are only marginally self-explanatory.

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 the action (Zoom) and the resource (rectangular window), and the four coordinate parameters directly support this. It also distinguishes from the sibling zoom_extents by specifying a rectangular window, though it doesn't explicitly mention the 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 provided on when to use this tool versus alternatives such as zoom_extents. The description gives no context for choosing a window zoom over other view operations.

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