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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior, so the description need not repeat those. It adds modest behavioral context by indicating what data can be retrieved, but it does not address edge cases like invalid LOINC format or nonexistent codes. This is acceptable given the strong annotation coverage.

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 tight, uses a short lead sentence and three scannable bullets, and includes a concrete example. Every sentence earns its place without 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?

With one well-documented parameter, strong annotations, and an output schema present, the description provides enough context for correct invocation. The bullets define the scope of returned details, and no additional operational guidance seems necessary.

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 schema already fully documents the single parameter with a pattern, example, and description. The description repeats the format and example, adding little beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

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 purpose: getting detailed information about a specific LOINC code, with a concise list of the kinds of details returned (name, component, property, timing, system, scale, method). It does not explicitly differentiate from siblings like loinc_search or loinc_panels, but the 'specific LOINC code' framing and the field list make the scope clear enough.

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 'Use this tool to' section provides concrete scenarios where this tool is appropriate, such as retrieving full LOINC metadata for a known code. It does not explicitly mention when not to use it or name alternatives, but the context is clear and actionable for an agent deciding to look up a code.

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