measure

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

The description states 'Installs the measurement on the scope', implying a side effect (configuration change). However, annotations declare readOnlyHint=true, indicating no side effects. This contradiction harms trust. Without this issue, the description adds some operational context beyond annotations.

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?

Two sentences with clear structure: first sentence states action, second lists common parameters and side effect. No wasted words, but could be slightly more informative about return value.

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?

With no output schema, the description should explain the return value format (e.g., number with units). It only says 'returns the value'. Missing details on what 'value' looks like, making it incomplete for an agent to handle the output.

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 coverage is 100% with descriptions for both parameters. The description lists common parameter values, adding marginal context. However, it does not explain what the returned value represents or any format details, so it adds only slight value beyond the schema.

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 clearly states verb and resource: 'Take a measurement on a channel.' It lists common parameters, but does not explicitly differentiate from the sibling tool 'measure_statistics', which likely does multi-measurement statistics. Slightly unclear distinction lowers the score.

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?

No guidance on when to use this tool versus alternatives like measure_statistics or get_waveform. The description does not mention appropriate contexts or when not to use it, leaving the agent with no decision support.

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