Generate SOAP note from transcript

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

No annotations are provided, so the description carries full burden. It discloses that billing codes are AI decision support, but does not discuss other behavioral aspects like potential errors, need for review, or limitations of the AI-generated content. Provides some transparency but incomplete.

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?

The description is two sentences long, front-loads the primary purpose, and every sentence adds value. It is appropriately sized for the tool's complexity.

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?

With 9 parameters (2 required) and no output schema, the description covers the main output (SOAP note structure) and optional features. It explains the specialty selection via reference to a sibling tool. Missing details on how patient or custom_instructions parameters affect the output, but overall sufficient for an agent to understand the tool's function and main inputs.

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%, so baseline is 3. The description adds context about optional outputs (billing codes, patient summary) but does not significantly expand on parameter meanings beyond what the schema provides. For example, 'patient' object description already says 'enrich the note.' Minimal added value.

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?

The description clearly states the tool generates a structured SOAP note from clinical transcript or shorthand, and lists optional additions like billing codes and patient summary. It effectively distinguishes from sibling 'transcribe_audio_to_soap' which handles audio input.

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 caution about billing codes requiring clinician review but lacks explicit guidance on when to use this tool vs alternatives like transcribe_audio_to_soap for audio input or list_specialties for available specialties. Usage context is implied but not directly addressed.

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