REW Measurement Workflow

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context beyond the schema: device selection, blocking mode, and result retrieval are handled automatically, and sweep measurements require a REW Pro license — a meaningful constraint an agent could not otherwise know. However, it says nothing about whether actions block until completion, what timing to expect for a sweep or sequence, or how failures in the signal chain surface.

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 and front-loaded, leading with the orchestration purpose before the action enumeration and the license caveat. The inline parenthetical glosses are efficient. The only structural flaw is the incomplete action list, which drops get_status while the schema enum includes it.

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?

This is a complex tool with four top-level parameters, three nested objects, no output schema, and no annotations, so the description is doing a lot of work. It covers the action vocabulary and the licensing constraint but leaves out what results are returned, how the nested measurement/sequence payloads map to specific actions, and the missing get_status action. Adequate to start, not complete for correct invocation of every branch.

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 description coverage is only 25% at the top level, so the description needs to compensate. It does add meaning to the 'action' enum by explaining what setup, calibrate_level, and measure_sequence actually do, which goes beyond the generic 'Workflow action to perform'. It does not explain the relationship between actions and the nested payload objects (setup, measurement, sequence), nor when each payload is required, and it omits get_status entirely.

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 gives a specific verb and resource ('Complete measurement workflow orchestration') and then enumerates the actions it orchestrates (setup, check_levels, calibrate_level, measure, measure_sequence) with a short gloss for each. It does not explicitly contrast itself with the many single-purpose siblings like rew_api_measure or rew_api_check_levels, so an agent must infer that this is the multi-step wrapper. Also, the 'get_status' action present in the enum is absent from the action list, leaving a gap in the stated 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?

Usage is only implied through the action list and the words 'Complete ... orchestration', which suggests multi-step flows rather than the single-shot siblings. There is no explicit statement of when to prefer this over rew_api_measure, rew_api_check_levels, or rew_api_measurement_session, and no preconditions such as requiring an existing connection via rew_api_connect. The license note is the one piece of genuine use-condition guidance.

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