map_loinc_to_snomed

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

Discloses key behaviors beyond annotations: returns only guidance (not mapping), explains licensing and availability constraints, and details why direct mapping is not available. Annotations (readOnlyHint, etc.) are consistent.

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?

Description is moderately sized but each sentence serves a purpose: defining action, clarifying limitations, providing rationale, and offering usage guidance. Well-structured with no redundancy.

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 no output schema, the description adequately explains the return type (guidance text). Covers purpose, limitations, and alternative tools completely, making it self-contained for an information-providing tool.

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?

Input schema has 100% coverage with pattern and description. Description adds value by providing an example ('2339-0' for Glucose) and clarifying expected format, making it more actionable.

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's specific verb ('looks up a LOINC code... and returns guidance') and resource (LOINC code), distinguishing it from siblings like loinc_search or loinc_details by focusing on mapping guidance.

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 states when to use ('for guidance on where to obtain mapping'), what it does not do ('does not perform the mapping'), and provides alternatives (UMLS, LOINC Expression Association files, SNOMED CT browser, RELMA).

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