configure_save

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about whether settings apply immediately or persist, whether they affect the instrument state, or what permissions/context are needed. The one behavioral constraint offered — that 'extra' accepts only documented :SAVE keywords — is useful but narrow.

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?

Purpose is front-loaded in one line, followed by a tight parameter-by-parameter list with no filler. Every clause adds a distinct piece of 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?

An output schema exists, so return values need not be explained, and all eight parameters are covered, making the definition largely self-sufficient for invocation. What is missing is the surrounding context — whether these settings persist and how this tool relates to the save/get-save siblings — which the description does not address.

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 0% and the schema contains no descriptions or enums, so the description is the sole source of parameter meaning. It documents all eight parameters, including enum-like values (COLor|GRAY, PNG|BMP|JPG), a length/format constraint on prefix (max 16 chars, no extension), a pathname example, and the accepted shape of 'extra' — exactly the compensation a 0%-coverage schema requires.

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 header 'Image/file saving options' combined with the per-field docs make it clear this configures how files/images are saved on the instrument. It is a noun phrase rather than an explicit verb+resource, and it never names a sibling such as get_save_config or save_image_on_instrument, so an agent gets the purpose but no routing signal.

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?

There is no statement of when to use this versus get_save_config, get_save_status, save_image_on_instrument, or save_waveform_on_instrument. No prerequisites or ordering (e.g. must it precede a save call?) are given, leaving the agent to infer usage entirely.

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