scope_capture

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.