afg2125_configure_sweep

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

Annotations show readOnlyHint=false, so it's a mutating operation. The description confirms it changes device state but adds no details about side effects, required output state, or whether it resets other settings. With no annotation support, this is a significant gap.

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 single sentence is concise and front-loaded with the key action. It contains no filler, but it lacks any structural breakdown for the five parameters. Still, it earns its place as a brief purpose statement.

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?

Given 5 parameters with no schema descriptions and only a terse one-liner, the description is incomplete for a configuration tool. It doesn't cover required parameters, spacing options beyond linear/log, or side effects. The output schema exists but doesn't reduce the need for parameter context.

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 description coverage is 0%, so the description must compensate, but it only hints at linear/logarithmic spacing. It doesn't explain start_frequency_hz, stop_frequency_hz, sweep_time_s, or source. The description adds minimal meaning over the bare parameter names.

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 clear action ('Enable and configure') on a specific resource ('frequency sweep') and distinguishes it from sibling modulation configs like AM/FM/FSK. The mention of linear/logarithmic adds specificity, but it doesn't explicitly name alternatives.

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?

No guidance on when to use this tool versus alternatives such as set_sweep_enabled or configure_am. The context is implied but not stated, and there are no exclusions or prerequisites.

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