osc_stop

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing beyond the action name: no mention of the resulting instrument state, idempotency, whether it aborts a wait-for-trigger,or what it returns. An output schema exists, but state-transition semantics remain undisclosed.

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?

One eight-word e sentence with zero filler; the action and object are front-loaded and every word earns its place. This is appropriately sized for a zero-parameter tool.

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?

Minimally viable for a zero-parameter control action with an output schema present, but it leaves clear gaps: no lifecycle context (stopping a continuous run vs. a single acquisition) and no note on whether stopping an already-stopped scope is an error or harmless.

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 tool has zero parameters and the empty schema fully covers them, so the baseline for 0 params applies. There is nothing for the description to add about parameter semantics.

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 verb ('Stop') and a specific resource ('acquisition on the oscilloscope'), making the action unambiguous. It does not explicitly contrast with siblings like osc_run or osc_single, but the 'stop' verb is distinctive within the sibling set.

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 on when to use this tool versus alternatives such as osc_single or osc_force_trigger. The intended context — halting a continuous run or aborting a single acquisition — must be inferred entirely from the sibling list rather than stated.

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