voice_record_and_transcribe

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

No annotations exist, so description fully discloses behavior: records audio, returns raw notes + temp WAV path, plays beeps (3 short+1 long at start, 1 at stop), explains polyphonic engine option and its dependency. Covers audio cues and return format.

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?

Front-loaded with core purpose, then return info, use case, beeps, polyphonic details. Efficient but could trim some detail; overall well-organized.

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?

Covers core functionality, return values, audio cues, and polyphonic option. Missing explanations for 4 parameters and no error/prerequisite info. Adequate but not 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 0%. Description explains only duration_sec and polyphonic but not device, min_note_sec, fmin_hz, fmax_hz. Incomplete for a 6-parameter tool.

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 it records microphone for specified duration and transcribes, with explicit use case 'inspect transcription before touching piano roll'. Distinguishes from siblings like voice_transcribe_file and voice_notes_to_piano_roll.

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 context for when to use ('inspect transcription before touching piano roll') and explains polyphonic vs monophonic options. Lacks explicit when-not-to-use or alternatives, but siblings are listed.

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