audio_record_start

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

No annotations are supplied, so the description carries the full behavioral burden. 'Start' implies a long-running operation that requires a separate stop call, but the description never says so, nor does it disclose where the WAV file is written, whether concurrent recordings are allowed, what happens if no device is tuned, or what error conditions exist.

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 front-loaded sentence that names the action, the signal type, the scope, and the file format with no filler. Nothing could be removed without losing meaning.

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 two-optional-parameter start tool with no output schema, the description covers the core intent but omits the operation lifecycle (it must be stopped via audio_record_stop) and the destination of the WAV file, both of which an agent needs to call this correctly.

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 100% with both parameters self-documented, so the baseline is 3. The description references FM/AM, which mirrors the modulation enum but adds no format or default guidance, and the 'description' parameter is not mentioned at all beyond what the schema already states.

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 (start recording) with the resource (demodulated audio, FM/AM) and the output artifact (WAV file), plus the scope constraint 'at the current frequency'. The 'demodulated audio' qualifier implicitly separates it from the raw-IQ sibling recording_start, but the description never names that sibling, so the differentiation is left to inference.

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?

'At the current frequency' implies the device must already be tuned and connected, which is useful implicit context. However there is no explicit when-to-use guidance, no mention that it pairs with audio_record_stop, and no statement of when to prefer this over recording_start or the other capture tools in the sibling list.

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