afg2125_set_ramp_symmetry

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

Annotations already indicate this is a mutating operation (readOnlyHint=false), and the description adds the valid range of 0-100 percent. However, it does not disclose side effects, failure conditions, or how the setting interacts with the current waveform, so behavioral transparency is minimal but not absent.

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 sentence that directly states the action and the range with no filler or redundant information. It is appropriately sized for the simplicity of the tool.

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 one-parameter setter with an output schema, the description covers the essential action and range. However, it omits important context such as when this setting applies (e.g., only for ramp waveforms) and any prerequisites, making it slightly incomplete.

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?

With 0% schema description coverage, the description compensates by specifying the valid numeric range (0 to 100 percent) for symmetry_percent. The parameter name is self-explanatory and the units are explicitly stated, giving the agent sufficient information to select an appropriate value.

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 uses a clear action verb ('Set') with a specific resource ('ramp symmetry') and a valid range. It effectively distinguishes this tool from sibling tools like afg2125_set_square_duty and afg2125_set_offset by targeting ramp symmetry specifically.

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 is provided on when to use this tool versus alternatives, nor are prerequisites mentioned (e.g., whether the ramp waveform must be selected first). The description simply states the action without any contextual cues.

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