Oscilloscope screenshot

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, yet the description still adds genuine behavioral detail: it disables the VISA termchar so an embedded 0x0A is not read as EOF, and it errors on non-image payloads instead of silently returning junk. That is exactly the kind of non-obvious context that prevents confusing failures. It does not say where/how the file lands.

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, front-loaded sentences with zero filler: the action first, then two concrete behavioral guarantees. Each sentence 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?

With four parameters, two of them entirely undocumented and no output schema, the description leaves meaningful gaps: what dialect/resource do, whether the return value is the written path, and what happens on timeout. For a tool whose schema carries so little, more explanation is warranted.

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 only 25% (just 'path'), and the description mentions no parameters at all. Two parameters, dialect and resource, are undocumented in both the schema and the description, and timeout_ms behavior/default is likewise unaddressed. The description does not compensate for the coverage gap.

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+resource ('Grab the scope display') and enumerates output formats (PNG/BMP/JPEG), making it clearly distinguishable from sibling waveform tools like scope_capture_waveform and export_waveform. It stops short of explicitly naming those siblings, so 4 rather than 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?

There is no statement of when to use this versus scope_capture_waveform, export_waveform, or scope_acquire in a crowded sibling set. Usage is only implied by the word 'screenshot'; no prerequisites or exclusions are given.

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