afg2125_set_amplitude

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

The description discloses a key behavioral trait beyond annotations: it 'enforces the offset/headroom limit', indicating the tool may adjust or reject values that exceed the limit. It also specifies 50-ohm output context. However, it doesn't detail the exact behavior on violation (clamp vs. error) or any side effects.

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 a single, well-structured sentence that front-loads the primary action and packs key constraints (50-ohm, Vpp, headroom enforcement) without extraneous words.

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 simple setter with one parameter and an output schema available, the description covers essential semantics: amplitude unit and the headroom limitation. It could mention whether the setting applies to the currently selected channel, but given its simplicity, this is adequate.

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 only parameter amplitude_vpp is given crucial context by the description: it is in Vpp and for a 50-ohm output. However, with 0% schema coverage, the description does not fully compensate—no range, minimum/maximum, or detailed constraint behavior is provided.

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 clearly states a specific action (set amplitude), the target resource (AFG2125 output), and the value semantics (50-ohm output amplitude in Vpp). It distinguishes itself from sibling tools like afg2125_set_frequency or afg2125_set_offset by including the headroom constraint.

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?

The description implies the use case (setting output amplitude) and hints that the tool automatically enforces the offset/headroom limit, but it does not explicitly state when to use this tool over alternatives or when not to use it. No direct comparison to similar setter tools is provided.

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