search_by_rxnorm_mapping

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'search' but doesn't clarify if this is a read-only operation, what the output format might be, whether there are rate limits, or if it requires specific permissions. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple search tool, making it easy to parse quickly.

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?

Given the complexity of RxNorm mappings and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'mappings' are, what the search returns, or how it relates to other mapping tools. For a tool in a domain with many siblings, more context is needed to guide effective use.

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 description coverage is 100%, with the parameter 'drugName' clearly documented as 'Drug name to search for in RxNorm mappings'. The description adds no additional meaning beyond this, such as examples, formatting hints, or search behavior details. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Search for RxNorm mappings by drug name' clearly states the action (search) and target (RxNorm mappings), but it's somewhat vague about what 'mappings' entail compared to siblings like 'get_mappings_by_rxcui' or 'get_rxnorm_mappings_by_pharmacologic_class'. It doesn't specify whether this searches for mappings to/from RxNorm or within RxNorm, leaving room for ambiguity.

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 description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_drug_names', 'get_mappings_by_rxcui', and 'get_rxnorm_mappings_by_pharmacologic_class', there's no indication of how this tool differs in context or scope, leaving the agent to guess based on the name alone.

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