measure_quick

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

No annotations are provided, so the description carries the full burden. It says 'Read', which suggests a non-destructive operation, and lists exactly which measurements are returned. However, it does not clarify acquisition prerequisites, side effects, or whether any setup is required.

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 operation and then lists the measurement set compactly. It avoids filler text, though the abbreviated measurement names may be opaque to an agent unfamiliar with oscilloscope terminology.

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. But given the single optional parameter, no annotations, and many measurement-related siblings, the description omits key usage context and parameter details needed for confident 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% for the single 'source' parameter. The description implies a channel scope ('on one channel'), which gives some meaning to the parameter, but it does not name the parameter, describe valid values, or mention the CH1 default.

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 ('Read') and resource ('common quick set on one channel'), then enumerates the exact measurement items. This distinguishes it from measurement setup/configuration siblings, though it does not name alternatives such as measure_item or measure_batch.

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 guidance on when to use this tool versus siblings like measure_item, measure_batch, or configure_quick. The phrase 'common quick set' implies a convenience path but does not state when it is or is not appropriate.

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