rew_measurement_cancel

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It declares a destructive action ('Cancel') with zero detail: no confirmation semantics, no statement about reversibility, no indication of what happens to data already collected, and no mention of the confirm flag behavior. For a cancel operation that has side effects, this is a significant gap.

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?

A single, clean sentence that is genuinely front-loaded and efficient. However, it contains no additional structural information beyond the bare verb+resource, and the under-2-word length borders on under-specification rather than disciplined conciseness.

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 tool is simple (one parameter, no output schema), so the bar is modest, but the description still leaves critical elements unexplained: the semantics of confirm, the effect of cancellation on a live measurement, and any expected return behavior. The agent cannot reliably call this tool correctly from the description alone.

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 0% and the description never mentions the sole parameter, confirm. The boolean's meaning - whether true confirms/cancels immediately or false requires extra confirmation, and what the tool returns at default false - is entirely unexplained. The description fails to compensate for the missing schema 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?

States a specific verb ('Cancel') and a precise resource ('a live REW measurement'), making the intent unmistakable. It implicitly differentiates from siblings like rew_measurement_execute and rew_measurement_plan (you cancel an in-progress measurement, not a planned or completed one), though it never names a sibling explicitly.

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 guidance on when to use this tool versus alternatives. It doesn't state a prerequisite (that a measurement must be actively live), doesn't mention the confirmation workflow, and doesn't distinguish itself from the similarly-purposed sibling audio_job_cancel. The agent is left to infer all usage context.

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