scope_measure_all

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

No annotations provided, so description carries full burden. It mentions transport (SCPI PAVA) but does not disclose side effects, error handling, or read-only nature. Minimal behavioral context beyond the purpose.

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 mostly concise but includes a verbose list of measurement names that could be shortened or omitted. Front-loaded with purpose, but some 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?

Output schema exists, so return details are covered. Description includes parameter range and list of measurements but lacks error conditions or behavior for invalid channels. Adequate but not complete.

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 0%, but description adds the valid range (1–4) for the channel parameter, which is not in the schema. This provides meaningful constraint beyond the integer type.

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?

Description clearly states the tool retrieves all automated measurements for a channel in one call, listing the specific measurements (MEAN, MAX, MIN, etc.). It distinguishes from siblings like scope_measure which likely returns individual measurements.

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?

Description implies use for batch measurement retrieval but lacks explicit guidance on when to use vs alternatives like scope_measure. No exclusion criteria or context for when this is appropriate.

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