start_recording

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

With no annotations, the description carries the full burden and does well: it discloses that the tool spawns transcribe_mic.py as a detached subprocess, that concurrency is limited to one active session, and it enumerates the return fields. It omits mic-permission requirements and failure modes, but the operational profile is substantially disclosed.

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 the one-line purpose, then structured Args/Returns blocks where each line earns its place. Slightly verbose in the model enumeration, but nothing is redundant or padded.

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 exists, yet the description supplies the return shape (session_id, transcript_path, pid, started_at, topic), documents all three parameters despite 0% schema coverage, and flags the single-session constraint. An agent has everything needed to invoke and interpret the call.

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 0%, so the description must compensate, and it does: topic semantics (used in filename, kebab-cased, defaults to 'recording'), model options enumerated with a recommendation, and language as an ISO code with default 'en'. This is meaning the bare schema does not provide.

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') plus resource ('local Whisper mic transcription session'), and the surrounding siblings (stop_recording, get_transcript) make the boundary unambiguous. An agent can immediately tell this initiates a capture session rather than reading or stopping one.

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?

Explicitly names the prerequisite alternative and the when-not condition: 'Only one session can be active at a time — call stop_recording first.' It also gives selection guidance for the model parameter ('small is a good balance for meetings'), which steers a reasonable default choice.

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