start_audio_capture

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

Without annotations, the description carries the full burden for behavioral disclosure. It mentions a precondition but does not disclose side effects, lifecycle (e.g., manual stop needed), return behavior, or error conditions. This is insufficient for a two-parameter tool with no output schema.

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?

Two sentences, no fluff. The essential precondition is front-loaded. Every sentence adds value. Excellent conciseness for the given content.

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?

Given no annotations, no output schema, and simple params, the description covers the basic precondition but lacks details on return values, how to stop capture, or whether it's asynchronous. It is minimally adequate but leaves gaps for an AI agent to infer behavior.

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?

Input schema provides 100% coverage with descriptions for both parameters (format and maxDuration). The tool description adds no extra information about parameters, so the baseline score of 3 is justified.

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?

Description clearly states the action (start capturing audio) and the resource (Strudel output). It distinguishes from sibling 'stop_audio_capture' by the verb 'start', though it does not explicitly differentiate from 'capture_audio_sample' which might serve a different purpose.

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 provides a precondition ('Audio must be playing for capture to work') which implies when to use, but it does not explicitly state when not to use or suggest alternatives among siblings. Usage context is implied rather than explicit.

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