Measurement Commands

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

There are no annotations, so the description carries the full behavioral burden, and it discloses almost nothing: whether execute mutates the measurement, changes hardware state, is reversible, requires the measurement to be active or connected, or what errors look like. The two-mode nature of the tool is stated but not the consequences of the mutating mode. This is a real gap for a command-execution tool.

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?

Two compact sentences, front-loaded with purpose followed by the action list. Nothing is redundant or padded. It could be marginally clearer by not leading with "Execute" when listing is one of the modes.

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 tool with a mutating mode, no annotations, and no output schema, the description leaves key questions unanswered: what list_commands returns, what a command string looks like, and what execute changes. The schema covers inputs but not behavior, so the definition is incomplete for correct invocation.

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 every parameter is already documented, including that command and parameters apply to the execute action. The description's parentheticals repeat that schema text rather than adding format, examples, or constraints. Baseline 3 is appropriate.

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 names a specific resource (per-measurement commands) and enumerates the two operations, list_commands and execute, so an agent can see the scope. The lead verb "Execute" is slightly misleading because the tool also only lists commands, but the action list corrects that. It does not differentiate from nearby siblings such as rew_api_measure or rew_api_measurement_session.

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?

It says nothing about when to call this versus the many sibling tools that also act on measurements, nor when to use list_commands before execute. The only usage signal, that command and parameters apply to the execute action, is already implicit in the schema. No prerequisites, ordering advice, or exclusions are given.

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