arb_disable_burst

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 states the core action but does not disclose side effects, prerequisites, whether burst must be active, or what happens if the instrument is in an incompatible state.

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 short, direct, and front-loaded with the purpose. The parameter documentation is compact and adds necessary information without padding.

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 one-parameter control operation, the description covers the essential scope and channel range. With an output schema present, return-value details are not required. It is adequate but could mention preconditions or interaction with other modulation modes.

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?

The description adds meaningful detail beyond the schema by specifying that channel must be 1 or 2. The schema only says 'integer', so this range constraint is valuable.

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 uses a specific verb and resource: 'Disable burst mode on a waveform generator channel.' This clearly distinguishes the tool from siblings like arb_set_burst and arb_disable_modulation.

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 itself: call this when burst mode needs to be turned off. However, the description does not explicitly state when to prefer this over related tools such as arb_disable_modulation or arb_disable_sweep.

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