search_answerlists

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

No annotations provided, so description carries full burden. Discloses relevance ranking (same as loinc.org/search UI), truncation behavior with character budget, and recommendation to call get_loinc for full records. Lacks explicit read-only statement but appropriate for a search tool.

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 coherent paragraph, front-loaded with purpose. Sentences are efficient, but could benefit from minor restructuring to separate behavior from parameter guidance.

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?

Covers key aspects: what is searched, ranking, truncation, pagination, and linkage to get_loinc. Missing parameter descriptions but otherwise complete for a search tool with no output schema.

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?

Schema coverage is 0%, but description only explains `offset` in context of pagination. Other parameters (rows, query, language, sortorder, include_facets) are not described, leaving the agent without guidance on their meaning or valid values.

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?

Explicitly states 'Search LOINC answer lists' with examples (e.g., smoking-status choices). Distinguishes from siblings by stating 'Use when you need the allowed answers for a term rather than the term itself.'

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 clear when-to-use vs alternatives, advises reformulating query instead of deep-paging when top hits miss, and explains pagination with `offset` for truncated results.

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