zoom_to_page

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

With no annotations, the description carries full burden for behavioral disclosure. It does not explain how 'zoom to fit' works, whether the zoomLevel parameter overrides 'fit' behavior, or any side effects on the view. The interaction between 'fit' and the zoomLevel parameter is unclear.

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 one sentence of six words, extremely concise. However, it may be too short to be fully helpful; but for a simple tool, it avoids verbosity.

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 the tool's simplicity and lack of output schema, the description is incomplete. It does not explain what 'fit page' means, how the zoomLevel parameter modifies behavior, or what the user can expect after invoking the 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?

Schema coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema. It does not clarify valid ranges for zoomLevel or the effect of omitting it.

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?

Description 'Zoom to fit page in view' clearly states the action (zoom) and target (page). It distinguishes from siblings like navigate_to_page or select_page by specifying the zoom operation, but does not explicitly differentiate from tools like adjust_page_layout, which may also affect 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?

No guidance on when to use this tool vs alternatives such as navigate_to_page or adjust_page_layout. The description lacks context on prerequisites, limitations, or scenarios where this tool is preferred.

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