search_loincs

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

Discloses relevance ranking, compact rows for triage, character-budget capped output, and pagination with offset. No annotations provided, so description carries full burden. Could mention read-only nature but otherwise transparent.

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?

Efficiently written with front-loaded purpose, then usage tips, ranking behavior, and pagination. No superfluous sentences.

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?

Provides good context for using the tool, including output format (TOON table) and when to use sibling tool. However, missing parameter descriptions and output schema details, leaving some gaps.

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?

Parameter schema coverage is 0%, but description only explains query and offset implicitly. Missing explanations for rows, language, sortorder, and include_facets, which are crucial for proper usage.

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 this tool searches LOINC terms, listing specific examples like lab tests, vital signs, and measurements. It distinguishes from siblings by mentioning get_loinc for drill-down and other search tools.

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?

Explicit guidance on when to use this tool (for any LOINC search by name or number), and when to reformulate queries instead of deep-paging. Also instructs to use get_loinc for full record details.

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