view

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

The readOnlyHint annotation is consistent with the operations described (zooming and capturing screenshots are non-mutating). The description adds useful details about each operation's effect, but it does not disclose potential nuances such as coordinate systems or error handling. The annotation lowers the burden, so the added context earns a 4.

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 succinct and well-structured, front-loading the main purpose and then using a clear list to detail operations. Every sentence contributes value without repetition 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?

Given the presence of an output schema and the read-only annotation, the description covers the operations adequately. It could be more explicit about which operation requires which parameters, but the overall context is sufficient for a viewport control tool.

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 description names the parameters for zoom_window (x1, y1, x2, y2) and lists operation options, but it does not explain the meaning of coordinates (units, system) or how parameters apply to other operations. With 0% schema coverage, the description partially compensates but leaves ambiguity for parameter requirements across operations.

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 tool's purpose as 'Viewport control and screenshot capture' and enumerates specific operations (zoom_extents, zoom_window, get_screenshot). This specific verb+resource framing clearly distinguishes it from sibling tools focused on layers, entities, 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 operation list implicitly guides when to use this tool (any zooming or screenshot need), and the context is clear. However, it does not explicitly mention when not to use it or contrast with alternatives, though the sibling list makes the separation obvious.

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