Search RxNorm Drugs

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds a return-value summary but does not disclose matching semantics, pagination, external API behavior, or rate limits. No contradiction with annotations.

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 front-loaded with a clear purpose sentence, followed by a compact bulleted list of use cases and a concise return-value summary. Every sentence earns its place without repetition or filler.

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 simple two-parameter surface, rich annotations, and presence of an output schema, the description covers what is needed for basic invocation. It could be more complete by explicitly directing users to sibling tools for concept details or NDC lookups, but that gap is not critical for a search operation.

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 description coverage is 100%, with both 'query' and 'max_results' already well documented (including default, min, max). The description's mention of brand/generic search aligns with the query parameter but adds no new semantic nuance beyond the schema, so baseline 3 is appropriate.

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 states a specific verb+resource ('Search for drugs in RxNorm') and enumerates concrete use cases: find by brand/generic, look up for prescribing, search formulations. It also specifies return values (RxCUI identifiers, names, term types), which clearly distinguishes it from sibling lookup tools like rxnorm_concept or rxnorm_ndc.

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?

A bulleted list gives clear usage contexts (brand/generic search, prescribing lookups, formulation search). However, it does not explicitly state when not to use the tool or name alternatives (e.g., rxnorm_concept for code-based lookup), so it lacks full exclusion guidance.

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