osc_set_acquire_mode

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

With no annotations, the description must disclose behavioral traits. It states only that the tool changes acquisition mode and gives no information about side effects, prerequisites, interaction with averaging, or whether the change 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 short, front-loaded with the purpose, and contains no filler. The argument documentation is compact, though it could be slightly more structured with a bulleted list.

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 one-parameter setter this is minimally adequate: it names the operation and valid inputs. However, it lacks practical context such as the relationship between AVERAGE mode and osc_set_average_count, and whether the instrument needs to be in a particular state.

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 schema only defines mode as a generic string with no enum, so the description adds the essential valid values (SAMPLING, PEAK_DETECT, AVERAGE). This compensates for the 0% schema coverage, though it does not explain the meaning of each mode.

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 and object: it sets the oscilloscope's acquisition mode. This clearly differentiates the tool from sibling setters like osc_set_timebase or osc_set_trigger_mode.

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?

No guidance is given about when this tool should be chosen, when it should not be used, or how it relates to alternatives such as osc_set_average_count. The only usage cue is implied by the tool's name and first sentence.

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