LOINC Code Details

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds detail about the returned fields but does not disclose additional behavioral traits such as error behavior, prerequisites, or rate limits. This meets the lower bar for annotated tools but offers no extra behavioral context.

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 concise and well-structured: a front-loaded purpose statement, a scannable bullet list of use cases, and a clear input format instruction. Every sentence earns its place, with no redundant elaboration.

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?

This is a simple single-parameter, read-only tool with an output schema available. The description fully explains what the tool does, what information it returns, and how to provide the LOINC number. No additional context is needed for an agent to invoke it correctly.

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?

The input schema has 100% description coverage for the single parameter, including pattern and an example. The tool description repeats the format and example ('XXXXX-X', '2339-0' for Glucose), which adds no meaningful information beyond what the schema already provides. Baseline of 3 applies.

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 'Get detailed information about a specific LOINC code' — a specific verb and resource. It enumerates the exact fields returned (full name, description, component, property, timing, system, scale type, method), which distinguishes it from siblings like loinc_search or loinc_answers.

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?

Provides a 'Use this tool to' list with clear scenarios, implying when to use it (when you have a specific LOINC code and need details). However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of full exclusions.

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