scope_screenshot

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

Discloses file saving behavior (subfolder, auto-filename), path returned, and transport method. Could mention if overwrite occurs or device state impact, but overall transparent.

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?

Front-loaded purpose with organized parameter list. Transport note adds technical depth but not strictly necessary; still concise overall.

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?

Covers all aspects: purpose, file saving, parameters, return value, and transport. No gaps given the lack of annotations.

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?

Parameter descriptions in the 'Args' section fully detail allowed values for image_format, area, and background, compensating for zero schema description coverage.

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?

Clearly states 'Capture the oscilloscope screen and save as a timestamped image file.' verb and resource, distinct from sibling tools like scope_save_waveform_csv.

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 explicit guidance on when to use vs alternatives like waveform capture. Implicitly clear from purpose but lacks when/why to choose screenshot over other data capture tools.

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