Zoom Window

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

The annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already structured. The description adds that the operation changes the display to a given rectangular region, which is useful but not deeply detailed; it does not state whether the viewport state is persistent or whether any viewport is specifically targeted.

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, tightly worded sentence that immediately conveys the tool's purpose. Every word contributes meaning, with no filler or redundant restatement of the title.

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 zoom operation with an output schema and 100% parameter coverage, the description is nearly complete. It could mention coordinate conventions or that this affects the current viewport, but the core calling context is clear enough for an agent to invoke it correctly.

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 100%, so the schema already documents all four parameters. The description adds only the generic notion of a 'rectangular window region' and does not explain corner ordering, coordinate system, or units beyond what the schema provides.

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 states a specific verb ('Zoom') and a precise resource ('display the specified rectangular window region'), clearly distinguishing it from siblings like view_zoom_extents and view_zoom_and_screenshot. There is no ambiguity about what operation is being described.

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 gives no guidance on when to use this tool versus alternatives such as view_zoom_extents or view_zoom_and_screenshot. An agent must infer the intended use case from the tool name and parameter schema alone.

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