lookup_medication

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

No annotations provided, so description carries full burden. It discloses source (MedlinePlus Connect) and acceptable inputs, but lacks details on failure modes, data freshness, or behavior if multiple identifiers are provided. Adequate but not comprehensive.

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 sentence conveys purpose, source, and input methods with no wasted words. Front-loaded and efficient.

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?

No output schema, yet description doesn't explain return format or provide examples. Lacks details on error handling or network requirements. For a simple lookup, it's adequate but leaves gaps for an agent.

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 covers all 4 params with descriptions (100% coverage). Description adds context: 'English name fallback' and that the tool uses codes or name. This extra clarity about fallback behavior justifies above baseline.

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?

Description clearly states verb 'look up', resource 'medication education links from MedlinePlus Connect', and acceptable identifiers (RXCUI, NDC, name). Distinguishes from sibling tools (lookup_diagnosis, etc.) by focusing solely on medications.

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?

Implies usage for medication lookups but offers no explicit guidance on when to use vs alternatives, when not to use, or prerequisites. The purpose alone differentiates from siblings, but no exclusions or decision tree.

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