usbtmc_screenshot_tektronix_display

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description adds the prerequisite that device_id comes from usbtmc_connect(), implying an active connection is needed. However, it does not explain capture behavior, potential failures, or format of the returned image.

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?

Description is a short, front-loaded purpose sentence followed by compact parameter and return notes. It avoids unnecessary prose, though the Args section duplicates schema info.

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 simple read-only capture tool with a single well-documented parameter and good annotations, the description covers the essential invocation details. It lacks explicit sibling differentiation and output format detail, but the name and annotations fill some gaps.

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?

The schema fully describes device_id with type, range, and provenance ('returned by usbtmc_connect()'). The description repeats this information without adding new semantics, so it provides no 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 'Capture screenshot from a Tektronix oscilloscope', providing a specific verb, resource, and brand distinction from the Keysight sibling tool. This fully defines the tool's purpose.

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 offers no guidance on when to use this tool versus the alternative usbtmc_screenshot_keysight_display. It does not mention device compatibility conditions or when not to use it.

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