resume_sweep

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

Annotations already declare this is a state-changing but non-destructive, non-open-world operation, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond the annotations — that resuming also restores the frequency array — but omits whether the call fails when no sweep is paused and how it interacts with an in-progress capture or measurement.

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?

A single front-loaded sentence with the verb and resource first and the parenthetical detail last. Nothing is wasted and nothing essential is buried.

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?

With an output schema present, return values need not be described, and the annotations cover the safety profile, so the description is nearly sufficient for a zero-argument tool. The one gap is the precondition (a paused sweep) that determines whether the call will succeed.

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 takes zero parameters, so there is no parameter semantics to explain; the empty schema is fully self-consistent with the description. Baseline 4 applies since the description cannot add parameter meaning where none exists.

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 ('Resume') and a specific resource ('the instrument's configured display sweep'), which is enough to distinguish it from the sibling pause_sweep by polarity alone. It stops short of explicitly naming pause_sweep as its counterpart, so it earns a 4 rather than a 5.

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?

Usage is only implied: an agent can infer this is the inverse of pause_sweep, but the description never says it should be called only when a sweep is paused, nor what happens if the sweep was never paused or the device is disconnected. No alternatives or preconditions are stated.

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