Zoom and Screenshot

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

With readOnlyHint=true already covering the safety profile, the description adds meaningful behavioral detail: zooming to extents by default, zooming to a window when coordinates are supplied, and then capturing a screenshot. This discloses the operation order and conditional behavior beyond the annotation.

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?

Two short sentences, front-loaded with the action and then the use case. There is no wasted text; every phrase contributes to selection and invocation.

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 read-only tool with only optional parameters and no output schema, the description covers what the tool does, when to use it, and the parameter-dependent behavior. It does not describe the exact screenshot return format, but that is implied and not critical for using the tool 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 coverage is 100%, and each parameter is already described. The description adds value by clarifying the conditional behavior: coordinates switch the zoom from extents to a window. This helps an agent understand that providing all four corner coordinates changes the zoom mode.

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 and resource: 'Zoom to extents (or window if coordinates given), then capture a screenshot.' This clearly distinguishes the tool from the sibling single-purpose tools view_zoom_extents, view_zoom_window, and view_screenshot by combining both actions into one workflow.

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 provides clear context: 'The most useful tool for visually inspecting drawing state.' This tells an agent when to prefer this tool. It does not explicitly name alternatives or state when not to use it, but the recommendation is strong and intelligible.

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