load_setup

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 reveals the file source and destination ('into the instrument') but does not say whether loading overwrites current settings, what permissions are required, or how errors are handled.

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 wasted words. It delivers the core action, source, and destination immediately.

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?

The output schema exists, so return values need not be explained, and the one-parameter operation is structurally simple. Still, the lack of annotations and the absence of side-effect or sibling-differentiation details leave meaningful gaps for safely invoking a state-changing load operation.

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 for the single 'filename' parameter. It does so by specifying that the file must be one previously written by save_setup, which meaningfully constrains the expected value, though it does not describe path or extension 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?

The description states a specific verb ('Load'), resource ('setup file'), and source ('previously written by save_setup'), so the core operation is clear. However, it does not distinguish this tool from the similar sibling 'load_setup_on_instrument', which could confuse an agent choosing between them.

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 phrase 'previously written by save_setup' implies the tool should be used after saving a setup, but it gives no explicit when-to-use guidance or alternatives. No condition or exclusion is stated for choosing between this and load_setup_on_instrument.

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