set_trigger_slope

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

No annotations are provided, so the description carries the full behavioral burden, and it only discloses the accepted enum values for polarity/when/window. It never states that this mutates instrument state, whether the trigger must be stopped first, how it interacts with source/level settings, or what happens to unspecified knobs.

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?

Three short lines, front-loaded with the trigger type and followed by a compact enum legend; nothing is padded. It is efficient, though the terse style borders on under-specification rather than disciplined brevity.

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 no explanation, but with 9 parameters, 0% schema coverage and no annotations, the definition leaves the majority of the calling surface undocumented. An agent cannot reliably set source, levels, or time bounds from this description alone.

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% across 9 parameters, so the description must compensate but only explains three of them (polarity, when, window). source, level_a, level_b, time_lower, time_upper and extra are entirely undocumented, including units for the time/level fields.

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 is a noun fragment, 'Slope (rise/fall time) trigger.', with no verb stating what is actually done to the trigger (configure, arm, enable). It identifies the trigger type, which loosely separates it from the many set_trigger_* siblings, but the name does most of that work rather than the description.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g. run state, acquisition mode), and no routing to alternatives such as set_trigger_edge or set_trigger_window. The enum legend describes value syntax, not usage context.

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