rew_stop_audio

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

Beyond the annotations, the description discloses two meaningful traits: the operation is best-effort ('Attempt to stop'), and it executes out-of-band rather than through the server's command wait queue, which matters for concurrency and ordering. This is consistent with destructiveHint=false and readOnlyHint=false, since halting signal output is a state change but not destructive.

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 dense sentence with the action front-loaded and no filler. The list of four targets plus the queue-bypass clause make it slightly information-heavy for one sentence, but nothing is wasted.

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 no parameters and no output schema, the description covers the essential scope and execution mode. The main residual gap is what 'attempt' failure looks like on return and whether all four targets must be stopped or only active ones, which would help a caller interpret the result.

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 the baseline is 4. The description correctly frames the scope as acting on all four signal types rather than requiring the caller to select one, which is the only semantic detail a parameterless tool needs here.

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 enumerates the affected resources (generator, sweep, stepped measurement, RTA), including that each is stopped independently. It is immediately clear what the tool does and how it differs from a generic command tool, though it does not name a specific sibling to contrast with.

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 implied rather than stated: 'bypassing this server's command wait queue' signals this is for immediate interruption instead of queuing a stop via the command path, presumably rew_command. There is no explicit 'use this when' or 'do not use when' sentence, so the agent must infer the selection rule.

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