load_setup_on_instrument

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the underlying SCPI command (:LOAD:SETup <path>) and that the file lives on the instrument, but says nothing about whether loading overwrites current settings, what happens on a missing/invalid file, or any required state.

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 the verb, resource, source, and the equivalent SCPI command — 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 explained, and the SCPI hint is useful. However, with no annotations and an ambiguous sibling (load_setup), the definition leaves the mutation semantics and the when-to-use decision unaddressed.

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?

With only one parameter and 0% schema description coverage, the description must compensate, and the embedded :LOAD:SETup <path> does clarify that the argument is an instrument-side file path rather than a host path. It does not give path syntax, extensions, or directory conventions.

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 (Load) and resource (.stp setup file) and pins down the source as the instrument's own storage, which implicitly separates it from the host-side load_setup sibling. It stops short of naming that sibling explicitly, so an agent must infer the routing.

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 never says when to use this versus load_setup, nor any prerequisite such as the file already existing on the instrument or the state change it causes. The source-of-file phrase hints at usage but provides no explicit condition or exclusion.

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