rew_input_level_check

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

With no annotations, the description carries the behavioral burden. It does disclose that no sweep is emitted and that capture is bounded, which suggests a non-stimulus monitoring operation. However, it does not mention whether the tool saves data, requires confirmation, or has any side effects.

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 two short, front-loaded sentences with no filler. Both sentences earn their place: one states the core action, the other clarifies a key behavioral distinction.

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?

There is no output schema and no annotations, so the description needed to explain what the capture returns and how confirm/durationMs are intended to be used. It does neither, leaving the agent to infer too much for a standalone tool.

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%, so the description needed to clarify the parameters. 'Bounded period' is a weak hint for durationMs, but confirm is not addressed at all, and no value is added beyond the schema's names/defaults/ranges.

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 a specific action ('Capture') and resource ('microphone input levels') over a bounded period. The clause 'This emits no sweep' explicitly distinguishes it from sweep-based sibling tools like rew_measurement_execute and rew_generate_trace.

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 'emits no sweep' phrase implies this is for level checks rather than full measurements, but the description never explicitly says when to use this tool versus alternatives. There is no direct guidance on prerequisites or when not to use it.

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