zoom_to_page

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

With no annotations provided, the description carries full burden but only states 'Zoom and fit page in view' without disclosing side effects, view mode changes, or zoom behavior (e.g., spread handling). This is minimal for a straightforward tool but insufficient for complex scenarios.

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 sentence of 5 words, which is concise but lacks structure. It does not front-load key details or use bullet points, but is appropriate for a simple tool.

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?

The tool has 2 parameters and no output schema. The description does not explain the zoom behavior or interaction with current page/spread. Given sibling tools, it is not complete enough for an agent to understand usage context.

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 50% (only 'pageIndex' has a description). The tool description adds no extra meaning for parameters; the 'fitOption' enum values are not explained. This falls short of compensating for the schema gap.

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 'Zoom and fit page in view' clearly indicates the tool's action (zoom/fit) and target (page), distinguishing it from sibling 'navigate_to_page' which likely changes page without zooming. However, it could be more specific about what 'fit' entails.

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?

No guidance is provided on when to use this tool versus alternatives like 'navigate_to_page' or other zoom options. The description does not mention any prerequisites or exclusions.

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