Resolve a supplement identity. Use mode='supplement_retail' only for raw retail product titles; it invokes the fail-closed retail front door. Identity mode is the default.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Explicit routing mode; retail titles require supplement_retail | identity |
| query | Yes | Supplement identity or raw retail product title |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so full burden on description. Mentions fail-closed retail front door for one mode, but lacks details on auth needs, rate limits, or whether it mutates data.
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?
Two concise sentences with critical information front-loaded. No wasted words.
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?
For a simple 2-param tool with no output schema, the description is largely complete. Could mention output format (e.g., returns supplement IDs) but not essential given sibling tools.
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 100%; description adds value by clarifying mode usage (retail titles require supplement_retail) and fail-closed behavior. Slight redundancy for query parameter.
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?
States it resolves a supplement identity and differentiates modes (identity vs supplement_retail). Could be more specific about what 'resolve' entails, but clear overall.
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?
Explicitly tells when to use supplement_retail mode (raw retail product titles) and mentions fail-closed behavior. But no guidance on when to use this vs sibling tools like get_supplement_info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: searching for supplements or conditions, retrieving supplement info, interactions, biomarker mappings, top brands. No overlap or ambiguity.
All tool names follow a consistent 'verb_noun' pattern with verbs 'get_' and 'search_', and nouns are appropriately plural or singular.
8 tools is well-scoped for a health supplement knowledge base, covering core queries without unnecessary complexity.
The tool set covers search, information retrieval, interactions, biomarker mapping, and brand quality, leaving no obvious gaps for a read-only reference server.