save_image_on_instrument

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

No annotations exist, so the description carries the full behavioral burden. It usefully clarifies that the image lands on instrument-local storage (C: internal vs D: USB) and gives filename/length constraints, but it omits whether an existing file is overwritten, whether a wait_complete is required, and what happens on a malformed path.

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 primary action is front-loaded in the first clause, followed by tightly scoped, indented parameter constraints. Every line conveys usable information with no filler.

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?

An output schema exists so return values need not be described, and the parameter constraints are well covered. What is missing for a zero-annotation mutation tool is overwrite/error semantics and the tool-side status check (e.g. get_save_status), keeping it just short of complete.

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 0%, so the description must compensate, and it does: it gives concrete path examples for internal disk and USB, enumerates allowed suffixes (.png, .bmp, .jpg), and states the 26-character filename limit. Only the exact SCPI argument quoting/escaping is left unstated.

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?

States a specific verb+resource ('Store the current screen image on the instrument's own storage') and even names the underlying SCPI command, which pins down the exact operation. The 'on the instrument's own storage' phrasing separates it from the many download-oriented siblings like get_screenshot and get_screenshot_data.

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 destination detail ('instrument's own storage') implies this is for on-device saving rather than retrieval, but the description never explicitly says when to prefer this over get_screenshot or the other save_* tools, nor does it state prerequisites. Usage is inferable, not stated.

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