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

Annotations only say readOnlyHint=false and destructiveHint=false, which is neutral. The description does not disclose side effects such as file creation during export, the behavior of last, or differences between preview and single. It does provide a return format, but that is more about results than 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 compact, front-loaded with the purpose, and structured with clear Return Format and Examples sections. Every line earns its place, and nothing is redundant with the schema.

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?

The description is adequate for basic invocation: it names the tool's function, shows a return format, and demonstrates common operation calls. However, it omits semantics for operations like export_summary and last, and does not clarify the capture-to-export workflow or what data will look like.

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%, so baseline is 3. The examples add value beyond the schema by showing that sample_rate_hz and sample_count are relevant to operation='single', while export_csv and preview use no explicit capture parameters. This helps an agent compose valid parameter combinations.

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 the tool acquires waveforms and exports capture data, using a specific verb and resource. It does not explicitly distinguish itself from sibling tools like scope_measure, but the core purpose is unambiguous.

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 examples imply usage patterns for operations like single, export_csv, and preview, but the description does not state when to choose this tool over alternatives such as scope_measure or scope_configure. Usage context is present implicitly, not explicitly.

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

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the mutating nature is known. The description adds a return format and concrete examples, which help an agent understand what to expect, but it does not disclose side effects such as overwriting existing settings or any device prerequisites. Some context is added, but the behavioral picture is incomplete.

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 compact and well-structured with a one-line purpose, a return format section, and three illustrative examples. Every part earns its place and there is no fluff or redundant detail.

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?

The description covers three of the four operations in the enum but omits an example or explanation for 'channels'. The return format is generic, and there is no output schema to clarify the data field. Given 9 parameters and 4 operations, the description provides a usable but incomplete picture for all possible invocations.

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 100%, so the baseline is 3. The description adds value by showing parameter-to-operation mappings through examples: channel_id/range_v/coupling for 'channel', waveform/frequency_hz for 'simulator_profile', and no params for 'get'. This helps an agent combine parameters correctly beyond the raw schema descriptions.

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: 'Configure oscilloscope channels and simulator signal profiles.' The examples further clarify distinct operations. The tool name and resource clearly differentiate it from sibling tools like scope_capture, scope_measure, and scope_trigger.

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 gives clear context that this tool is for configuration rather than capture or measurement, but it does not explicitly say when to use this tool versus alternatives, nor does it mention any exclusions. Usage is implied through the examples and operation enum rather than stated directly.

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

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

Annotations only provide readOnlyHint=false and destructiveHint=false. The description adds a generic return format and mentions session connection and health status, but it does not disclose consequences such as what 'connect' does to an existing session, whether 'disconnect' closes resources, or what data 'capabilities' returns. No contradiction with annotations, but behavioral depth is limited.

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 tool's purpose, followed by a compact return format and four representative examples. Each section contributes useful information, and there is no filler or redundancy.

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?

For a multi-operation device-management tool with no output schema, the return contract and examples are helpful. Minor gaps remain: the 'capabilities' operation is not exemplified, and the relationship to sibling tools is not spelled out, but the enum and parameter descriptions cover most mechanical detail.

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 100%, so the schema already documents operation, device_id, and backend. The examples illustrate valid combinations such as device_id='sim-001' but do not add substantive meaning beyond what the schema already provides.

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 opens with specific verbs and a clear resource: 'Discover, connect, and manage USB oscilloscope devices.' It then enumerates the consolidated responsibilities — device enumeration, session connection, backend selection, and health status — which effectively distinguishes it from the capture, configure, measure, and trigger siblings.

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?

Usage context is implied through the operation list and examples, but the description never explicitly tells an agent when to use scope_device versus scope_capture, scope_configure, or scope_measure. There are no exclusions or direct references to alternative tools.

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

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

The readOnlyHint annotation already covers the safety profile, and the description adds a return-format specification, which is useful. It does not describe deeper behavioral traits such as whether lookups are local, cached, or network-dependent, but for a read-only help tool the annotation plus return format is adequate.

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 compact and well-structured, with a short purpose statement, a return-format block, and three representative examples. Every sentence earns its place and the most actionable information is front-loaded.

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?

For a read-only help tool with a fully documented schema, the description is largely complete: it gives the return format, examples for key operations, and an overview of the help categories. It could clarify parameter combinations such as whether tool_name is required for operation='tool_help', but the schema and examples provide enough context for an agent to proceed.

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 100%, so the schema already documents all three parameters. The description adds little beyond examples that use the operation parameter, and it does not clarify how topic or tool_name interact with specific operations. This matches the baseline for fully documented schemas.

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 identifies the tool as the help/discovery/hardware-guidance entry point for oscilloscope-mcp, with examples of operations that reinforce its meta-role. It does not explicitly differentiate itself from the sibling scope_* tools, but its purpose as a help tool is reasonably distinct from capture/configure/device/measure/trigger.

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 provides examples but no explicit guidance on when to use this tool versus the sibling tools. It does not state 'use when you need documentation or operation assistance' or mention any conditions or exclusions. Usage context is only implied by the tool name and operation examples.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral details beyond annotations: the default reuse of the last capture, the fact that 'fresh' triggers a new capture, and the return envelope structure. These are meaningful operational traits not present in the 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?

The description is compact, front-loaded, and well-structured with a purpose statement, default-behavior note, return format, and examples. Every section earns its place, and the examples are concise without redundant prose.

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?

For a tool with four parameters, one required, and a moderate enum, the description provides enough context: it explains the core behavior, the fresh-capture exception, and the return format. It does not describe every possible operation in prose, but the schema covers the enum and parameter constraints, so no critical selection or invocation detail is missing.

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 100%, so the baseline is 3. The description goes beyond the schema by illustrating realistic invocation patterns and clarifying that sample_rate_hz is relevant to a 'fresh' capture. It does not explain every enum value, but the schema and examples together provide sufficient meaning.

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 ('Measure') with a clear resource ('voltage and timing parameters from captured waveforms'), immediately distinguishing it from sibling tools like scope_capture and scope_trigger. The operation names in the schema reinforce the intended purpose without ambiguity.

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 clearly states the default behavior ('Uses the last capture by default') and the fresh-capture alternative, giving an agent context on when to use this tool versus performing a capture first. It does not explicitly name alternatives or exclusions, but the usage context is unambiguous enough for correct selection.

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

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries the burden of disclosing side effects. It mentions configure/inspect and gives a return format, but it does not explain the behavioral effects of arm or force operations, which are not covered by the phrase 'configure and inspect.' The risk of mutating oscilloscope trigger state is not clarified.

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 short and front-loaded: one purpose sentence, the return format, and two representative examples. There is no filler or repetition of schema content. It is well organized and every section earns its place.

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?

The tool is moderately complex with four operation modes, but the description only covers set and get in examples, leaving arm and force semantically undefined. There is no mention of behavior with null parameters, channel validity, or interaction with scope_capture/scope_configure. The return format helps, but the missing operation semantics make the definition incomplete for correct invocation across all valid inputs.

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 100%, so the baseline is 3. The examples add value beyond the schema by showing that operation='get' can be called without the optional parameters while operation='set' uses threshold_v, mode, edge, and source_channel together. This gives the agent a concrete model of how the parameters combine, which the enum descriptions alone do not convey.

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 opens with a specific action-and-resource pair: 'Configure and inspect oscilloscope trigger settings.' This clearly identifies the tool's domain and distinguishes it from capture/measure/device siblings by the 'trigger' keyword. However, it does not explicitly differentiate from the sibling scope_configure, and 'configure' overlaps with that tool's likely purpose, so it falls short of a 5.

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 provides no guidance on when to choose this tool over scope_configure or other siblings, nor does it state prerequisites or exclusions. The examples illustrate set and get calls but do not explain when arm or force should be used or when a different scope tool would be more appropriate. Usage context must be inferred entirely from the tool name and the word 'trigger.'

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