zoom

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic action and does not explain what happens to the camera orientation, zoom level, or persistency, nor whether the view is reset or adjusted relative to the current state. This is a significant gap for a view manipulation tool.

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, front-loaded sentence with no redundant words or filler. It is appropriately concise for a simple tool, though it could be slightly expanded to include usage context without becoming verbose.

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 having a complete parameter schema and an output schema, the description lacks behavioral transparency and usage guidelines. Given the large set of sibling view-related tools, the absence of contextual differentiators makes the description insufficient for an agent to reliably decide when and how to invoke this 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 input schema provides full descriptions for both parameters ('buffer' and 'selection'), covering 100% of the parameter semantics. The description itself adds no additional meaning beyond restating the 'selection' concept, so it does not exceed the baseline provided by the schema.

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 'Zooms the view on a selection' clearly states the tool's action (zooming), the resource (view), and the target (selection). It is specific enough to suggest a camera/view adjustment, but it does not explicitly distinguish itself from sibling tools like 'orient' or 'center' which also affect the 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 provides no guidance on when to prefer this tool over alternatives such as 'center', 'orient', or 'reset'. There is no mention of typical use cases, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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