hackrf_set_tx_gain

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it. It does not say whether the change takes effect immediately on an active stream, whether it requires the device to be connected or idle, or whether the value is clamped or persisted.

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 short, front-loaded sentence with the resource named first and the range as a parenthetical. Efficient, though the brevity is partly a symptom of thin content rather than tight editing of rich content.

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 trivial one-parameter setter with no output schema, the essentials of what the parameter means are covered. Missing is the operational context an agent needs: when the device must be connected, whether the call succeeds on hardware without TX capability, and how it differs from the generic gain tool.

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?

Schema coverage is 100% with an explicit 'TX VGA gain in dB (0-47)' description and min/max bounds, so the single parameter is already fully documented structurally. The description merely repeats the same range, adding no new meaning, which lands at the baseline for high coverage.

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 and resource ('Set HackRF transmit gain') and gives the valid range, which distinguishes it from a generic gain-setter. However it never explicitly contrasts itself with the sibling sdr_set_gain, so an agent must infer which one applies to the HackRF TX chain.

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?

There is no when-to-use guidance at all: nothing about ordering relative to sdr_connect or a start of transmission, no note on hardware support, and no mention of when to prefer sdr_set_gain. The range hint is the only contextual cue the agent gets.

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