agilent33500b_configure_sweep

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

Annotations provide no safety hints (all false), and the description only says 'configure,' which implies a write operation but gives no details about side effects, prerequisites, or impact on other settings. It does not disclose whether enabling sweep disables burst or modulation, or any other behavioral traits.

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 with no unnecessary words. It front-loads the core action and parameters, making it highly efficient and easy to parse.

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 the tool has 7 parameters, 2 required, and zero schema coverage, the description is far too brief. It fails to explain the meaning of start/stop frequencies, sweep time, or the 'enabled' flag, and does not mention any constraints or relationships between parameters. The output schema may help, but the description itself is inadequate for an agent to confidently use the 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. It mentions spacing, trigger source, and marker, but leaves start_frequency_hz, stop_frequency_hz, sweep_time_s, and enabled unexplained. The description does not even clarify that start/stop frequencies are required or their units, making it insufficient for correct invocation.

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 specific verb ('configure') and resource ('sweep'), and explicitly mentions key aspects like linear/log spacing, trigger source, and optional Sync marker. This clearly distinguishes it from sibling tools such as configure_burst or configure_modulation.

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 usage for sweep configuration but does not explicitly state when to use this tool over alternatives like configure_burst or configure_modulation. There is no mention of prerequisites or when not to use it, leaving the agent with only the tool name and minimal context.

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