save_setup

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

No annotations are supplied, so the description carries the burden alone. It usefully reveals that this wraps the read-only :SYSTem:SETup? query and writes to a local file, but says nothing about where a default filename lands, overwrite behavior, or any required permissions.

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?

A single front-loaded sentence with no filler and the SCPI reference placed inline. Efficient, though it is short enough that conciseness is not really being tested.

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. Still, for a tool sitting in a crowded save/load family with no annotations, the description leaves the local-vs-instrument distinction and filename behavior unresolved.

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% and the sole 'filename' parameter has a null default whose meaning is never explained. The description adds no format, path, or default-behavior information, so it fails to compensate for the coverage gap.

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 gives a specific verb+resource ('Save the complete instrument setup') and even names the underlying SCPI query (:SYSTem:SETup?), which makes the operation concrete. It does not, however, distinguish itself from the sibling save_setup_on_instrument, leaving the 'local file' vs 'on instrument' split to be inferred.

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 when-to-use guidance and no mention of alternatives, despite siblings load_setup, load_setup_on_instrument, and save_setup_on_instrument forming an obvious decision set. The agent must guess which save/load variant applies.

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