Audio recording → SOAP note

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

With no annotations, description bears full burden for behavioral traits. It discloses async processing, waiting behavior, and supported file formats. Missing details on error handling, file storage, or size limits. Adequate but not thorough.

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, front-loaded with core action and key behaviors. No redundant information; every word 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?

Given 12 parameters, nested objects, and multiple optional features (include_* options, specialty, patient info), the description only covers audio input and output format. Does not mention customization options or output structure, leaving significant gaps for agent understanding.

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 covers 50% of parameters with descriptions. Description reinforces audio_path and async behavior (wait_for_completion, timeout_seconds) but does not explain other parameters like patient, template, or custom_instructions. Adds marginal value beyond schema.

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 specific verb 'transcribe' and resource 'audio recording to SOAP note', and distinguishes it from siblings like 'list_specialties' and 'generate_soap_note' by focusing on audio input. The supported formats and behavior (sync/async) further clarify 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?

Description implies use when you have a local audio recording of a clinical encounter, and mentions short vs long recordings with async behavior. However, it does not explicitly state when not to use this tool (e.g., for transcript-only tasks) or list alternatives among siblings. Usage is implied but not exhaustive.

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