ui_set_zoom

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

No annotations are provided, so the description carries full burden. It mentions zoom_level is between min and max but does not specify the range. It lacks details on fit_mode values, error handling, or side effects. Minimal disclosure of behavior.

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 that front-loads the purpose ('Set the document preview zoom') and then succinctly describes parameters. No redundant or extraneous information.

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 setter tool with only two parameters and no output schema, the description is minimally complete. It could be improved by specifying the allowed range for zoom_level or default behavior, but it covers the core functionality.

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% with parameter descriptions. The description adds slight value by indicating a range constraint for zoom_level ('between min and max') and repeating fit_mode examples. This is adequate but adds little beyond 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?

Clearly states it sets the document preview zoom, specifying both parameters (zoom_level and fit_mode). While it does not explicitly differentiate from sibling tools like ui_get_zoom, the verb 'set' and mention of parameters make the purpose clear.

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 versus alternatives (e.g., ui_get_zoom for reading, other ui_set_* tools for different settings). The description does not mention when not to use it or provide any contextual usage hints.

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