studio_zoom

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

With no annotations, the description fully discloses behavior: 'Captions stay screen-fixed; the content scales under them' and warns about zoom state inheritance and need for reset. This informs the agent of side effects and required cleanup.

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 sentences only, each with high impact. First sentence defines purpose and behavior; second sentence gives essential usage rule. No wasted words.

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 no annotations or output schema, the description covers purpose, behavior, usage constraints, and parameter context. Slightly lacks details on return value or completion signal, but sufficient for correct invocation.

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%, so base is 3. The description adds value by explaining reset purpose, suggesting max zoom scale (≤2.2), and providing defaults (1.7, 1100ms). This goes beyond the schema's basic descriptions.

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 explicitly states 'Camera punch-in: smoothly zoom the page toward a target' and identifies it as 'the money shot for a metric, button, or result,' clearly defining the action and resource. Differentiates from siblings like studio_click or studio_screenshot.

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?

Provides explicit when-to-use ('the money shot for a metric, button, or result') and a critical usage rule: 'ALWAYS studio_zoom with reset=true before navigating or showing the end card, or the next scene inherits the zoom.' This gives clear context and prevents misuse.

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