zoom_view

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

With no annotations, the description reveals the multiplicative zoom behavior but does not disclose potential side effects or limitations (e.g., whether the zoom is relative to current view or absolute).

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?

Single sentence with no redundant information, efficiently conveying the core functionality.

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 tool with one optional parameter, the description is nearly complete; it could mention that factor should be positive, but the functionality is well-covered.

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 explains the factor parameter's meaning (>1 zoom in, <1 zoom out) adding value beyond the schema which only provides a default and type.

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 view) and the effect (multiplicative factor) with explicit conditions for zoom in/out, distinguishing it from siblings like rotate_view.

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 implicitly conveys when to use (to zoom the view) but does not provide explicit guidance on when not to use or alternatives beyond what is obvious from the sibling list.

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