arb_set_sweep

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool enables a frequency sweep and lists parameters; it does not disclose side effects, whether existing modulation/burst modes are overridden, permissions required, or what happens on the device after invocation.

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 minimal and well-structured: one concise purpose sentence followed by a compact parameter list. Every sentence earns its place and there is no redundant or filler content.

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 parameter list is complete and an output schema exists, so return-value documentation is not required. However, the description lacks important operational context such as interactions with modulation, burst, or output-state settings, which matters for a device-control tool with no annotations.

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%, but the description compensates by explaining all four parameters clearly: channel range (1 or 2), start and stop frequencies in Hz, and sweep time in seconds. This adds meaningful unit and constraint information beyond the bare schema types and titles.

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 action—"Enable frequency sweep on the waveform generator"—with a clear verb and resource. It implicitly distinguishes itself from sibling tools like arb_set_frequency (fixed frequency) and arb_disable_sweep (disabling sweep).

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 intended use is implied by the action verb and the sibling tool arb_disable_sweep, but the description does not explicitly state when to choose this tool over alternatives or mention exclusions. It provides no direct usage guidance beyond the operation itself.

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