load_mask_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 burden. It discloses the underlying SCPI command (:LOAD:MASK) and the storage location, which is useful behavioral context, but does not state permission requirements, failure modes (e.g., missing file), or side effects on the current mask configuration.

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 clause that front-loads the action and resource, with the SCPI command in parentheses. No wasted words.

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. However, with zero annotations and no parameter description, the definition leaves the agent without guidance on required storage prerequisites or error behavior for a 1-param mutation tool.

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 single 'path' parameter is undocumented in both schema and description. The description implies the path refers to instrument-local storage but does not clarify format, root directory, or valid extensions beyond '.pf'.

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 (.pf mask file) and clarifies the source location ('from the instrument's own storage'), distinguishing it from save_mask_on_instrument and load_setup_on_instrument siblings.

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?

No indication of when to use this versus alternatives like configure_mask or load_setup_on_instrument, nor prerequisites such as whether a mask must first exist on the instrument's storage.

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