configure_bode

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

No annotations are provided, so the description must carry the behavioral burden. It discloses useful constraints (start*10 <= stop, voltage ranges, gain/phase curves settable only while stopped), but omits what run and enable do and whether changes are immediate or reversible for a mutation tool.

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?

Front-loaded with the tool purpose and prerequisite, then organized as concise per-parameter lines. It is dense but appropriate for a 12-parameter tool; no sentence is wasted on repetition.

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?

An output schema exists, so return values need not be explained. However, the description omits run/enable semantics and gives no routing guidance versus get_bode_config, leaving gaps for a complex, annotation-free mutation 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 description coverage is 0%, so the description must compensate, and it does for 10 of 12 parameters: sweep_type aliases, ref_in/ref_out channel forms, frequency bounds, points range, voltage bounds, voltage_range forms, and the stopped-state condition. It omits run and enable entirely, which is a notable gap in an otherwise rich parameter explanation.

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?

States a specific verb+resource: 'Bode plot configuration'. The purpose is clear from the name and description, but it does not explicitly differentiate from the sibling get_bode_config, which reads the same configuration.

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 states a prerequisite ('requires generator option') and a manual reference, but gives no explicit when-to-use guidance relative to alternatives such as get_bode_config or configure_awg. Usage is only implied by the configuration verb.

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