write_soap_draft

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

No annotations exist; description only says 'from AI-generated content' but fails to disclose mutation behavior, idempotency, permissions, or effects on existing data.

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?

Single sentence is concise but under-informative; no wasted words but fails to provide necessary detail for such a complex tool.

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?

Tool has 3 required parameters including a nested object with 5 fields, no output schema, and no parameter descriptions; agent cannot understand how to construct valid input from this definition.

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?

0% schema description coverage; description adds zero meaning to any parameter (exam_id, soap, clinic_id) beyond their JSON structure. No explanation of what each field represents.

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 uses specific verb 'create' and resource 'draft SOAP note', clearly distinguishing from sibling tools (get_patient_overview, get_soap_history, query_problem_list, search_clinical_notes) which are read-oriented.

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?

No guidance on when to use this tool vs alternatives, no prerequisites or when-not-to-use conditions provided.

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