afg2125_set_frequency

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

The description discloses that frequency is constrained by an AFG-2125 limit and that the function parameter can be selected or supplied. It does not describe error handling or clamping behavior if the limit is exceeded, but the limit note adds some value beyond the annotations, which are all false.

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 concise sentence that front-loads the action and includes only essential scoping details, with no unnecessary 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 an output schema available, the description adequately covers the purpose, the function parameter semantics, and the device limit. It does not explain what happens if the requested frequency is out of range, but that is a minor gap for this 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?

The phrase 'selected or supplied function' clarifies that the optional 'function' parameter defaults to the currently selected function when not supplied, adding meaning beyond the schema's bare nullable default. The required frequency_hz is self-explanatory from its name.

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 the action (Set), the resource (frequency), and the scope (within AFG-2125 limit, for the selected or supplied function). It distinguishes this from sibling tools that set other parameters like amplitude, offset, or duty cycle.

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 provides clear context that this tool sets frequency, which distinguishes it from alternatives. However, it does not explicitly mention when not to use it or name alternative tools for other waveform parameters.

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