audio_capture

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

No annotations provided, so description carries full burden. It discloses singleton conflict (server-wide), requirement that audio must be playing, and return values (base64 for sample). Could be more explicit about error handling (e.g., stop without start), but overall sufficient.

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?

Well-structured, front-loaded with purpose, then actions, example, alternatives, and caveat. Every sentence adds value, though slightly verbose. Could be tightened slightly but still effective.

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?

No output schema or annotations, but description covers actions, required audio, singleton conflict, and example. Lacks error scenarios and full return format details, but given complexity of a 5-param tool, it is reasonably complete.

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%, baseline 3. Description adds significant context: explains each action's behavior against the action enum, and provides important caveat about concurrent conflict for session_id. This exceeds baseline.

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?

Clearly states it records audio output from live Strudel session. Distinguishes actions (start, stop, sample) and explicitly mentions alternatives (export_midi, diagnostics), making it distinguishable from siblings.

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?

Provides explicit when-to-use guidance for each action (start, stop, sample) and context that audio must be playing. Also gives alternatives for MIDI export and diagnostics, excluding inappropriate uses.

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