romaco_set_zoom

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

No annotations are provided, so the description must carry the full burden. It discloses that zoom is cumulative per call and mentions the default factor and reset alternative. However, it does not describe potential side effects, permissions needed, or behavior at extremes (e.g., max/min zoom level). This is adequate but not comprehensive.

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 very concise: three sentences, no fluff. The first sentence states the main purpose, and subsequent sentences add essential usage details. Every sentence earns its place.

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 low-complexity tool with full schema coverage and no output schema, the description is largely complete. It covers purpose, usage, and resetting. It could mention that zoom affects the current pane or visible range, but overall it is adequate.

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 description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema: it restates the default factor and notes that calls are cumulative. The schema already describes factor, direction, and their meanings.

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 clearly states the tool's purpose: 'Zoom the chart in or out.' It specifies the action (zoom) and resource (chart), and distinguishes from siblings by mentioning 'Use romaco_reset_view to return to default fit.' No other sibling zoom tool exists.

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 explains how to use the tool: 'Each call zooms by the given factor (default 1.5x). Call multiple times for more zoom.' It also advises when to use an alternative: 'Use romaco_reset_view to return to default fit.' It does not explicitly state when not to use it, but the context is clear.

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