measure_statistics_item

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that enable=True sends the write form (:MEASure:STATistic:ITEM) to turn on statistics, and it lists accepted statistic and source forms. It does not cover permissions, persistence, side effects on subsequent reads, or whether the write is destructive.

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 front-loaded with the core purpose and then compactly enumerates relevant parameter forms. It avoids wasted words and uses line breaks effectively. The dense SCPI notation is efficient, though a bit terse for an agent unfamiliar with the instrument.

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 described. The description covers most parameter semantics and enable behavior. However, the required 'item' parameter is undefined, and there is no guidance on when to prefer this tool over siblings, leaving a notable gap for correct invocation.

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 does well for statistic (MAXimum|MINimum|CURRent|AVERages|DEViation|CNT, short forms ok), source (CH1..CH4 / MATH1..4 / D0..D15), source2 (only for delay/phase items), and enable=True semantics. The required 'item' parameter remains unexplained in both schema and description, preventing a higher score.

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 specific verb and resource: 'Read one statistic of a measurement item, or enable item statistics.' It distinguishes the two modes (read vs. enable) and names the SCPI write form used for enabling. However, it does not explicitly contrast with close siblings such as measure_item or set_measure_statistics.

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 explicit guidance on when to choose this tool over alternatives like measure_item or set_measure_statistics. The only usage clue is the enable=True behavior, which is about how to use a parameter rather than when to select this tool versus its siblings.

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