sdg1062x_configure_sweep

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

Annotations are all false (readOnlyHint=false, destructiveHint=false, etc.), so the description carries the full burden. It says 'configure' implying a write operation, but it does not disclose whether the sweep is immediately enabled, whether it modifies existing output settings, or any side effects. The phrase about sweep types adds a small behavioral hint but not enough.

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?

The description is a single sentence with no filler, making it concise and front-loaded. However, it is under-specified, but conciseness is about efficiency of prose, and this is efficient albeit too brief.

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?

With 8 parameters, 3 required, and no schema descriptions, a one-sentence description is insufficient for an agent to correctly invoke the tool. The output schema exists, so return value details are covered elsewhere, but parameter semantics, ordering, and interaction between start/stop frequency and spacing are left 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?

Schema description coverage is 0%, so the description must compensate. It only hints at the 'spacing' parameter via 'linear, logarithmic, or stepped' but leaves the other seven parameters unexplained (e.g., start/stop frequency, sweep time, direction, trigger source). This is minimal value added over the bare schema.

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 clearly states the tool configures a frequency sweep and lists the three supported types (linear, logarithmic, stepped). It distinguishes from other configure_* tools on the same instrument (modulation, burst, sync) by naming the sweep resource. It doesn't differentiate from sweep tools on other instruments, but the tool name provides that context.

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 guidance on when to use this tool vs alternatives, such as whether to use this before enabling the output or how it interacts with set_waveform. No exclusions or prerequisites are mentioned. This is a lack of any usage direction, warranting a score of 2.

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