audio

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

With no annotations provided, the description carries the full behavioral disclosure burden. It covers the probe lifecycle, timeout behavior, and the dBFS-bucket output shape. It does not describe response details or potential side effects, but it is reasonably transparent for a measurement 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?

The description is three short sentences with no filler. The purpose is front-loaded, followed by the key usage rule and a critical timeout constraint. Every sentence earns its place.

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 19-parameter tool with no output schema and no annotations, the description is minimally viable but leaves gaps: it does not indicate which parameters matter for start vs status vs stop, nor what the probe result looks like. The core usage sequence is covered, but an agent would still need to infer much of the invocation context from parameter names.

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 89%, so the schema already documents most parameters. The description adds value by explaining the relationship between start/status/stop through the probe lifecycle, which is not fully apparent from the schema enums alone.

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 states a specific verb ('Measure'), resource ('audio'), and output format ('compact dBFS buckets'), making the core purpose clear. It does not explicitly distinguish itself from sibling tools like 'record', so it stops short of a 5.

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 description gives concrete operational guidance: start a probe before requesting status or stopping, and expects a 90-second timeout. It does not explain when to choose this tool over alternatives, but the sequencing advice is clear and useful.

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