arb_set_burst

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does not explain what enabling burst mode does to current settings, whether it overrides other modes, requires an enabled output, or takes effect immediately.

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 very concise and front-loaded with the primary action. The Args block is cleanly organized and every line contributes useful semantic detail without redundancy.

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?

For a simple setter with three required parameters, the action and parameters are documented adequately. However, the lack of behavioral context, no mention of the disabling counterpart, and no annotations leave the agent without guidance on side effects or when to choose this 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?

With 0% schema description coverage, the Args block compensates by adding meaning: channel is scoped to 1 or 2, cycles is defined as burst cycles, and period is given in seconds. This goes beyond the bare property names in the 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 verb and resource: 'Enable burst mode on the waveform generator.' It identifies the tool as a burst-mode enable action and is distinguishable from the sibling arb_disable_burst, though it does not name that alternative explicitly.

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 versus alternatives like arb_disable_burst, arb_set_sweep, or modulation controls. The description states only the action and parameters, leaving usage decisions entirely to inference.

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