RxNorm Drug Classes

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

Annotations already thoroughly cover safety traits (readOnlyHint, idempotentHint, destructiveHint), lowering the bar for behavioral disclosure. The description adds a sentence about return contents (class IDs, names, sources) but does not discuss error handling, rate limits, or other behavioral nuances. This provides some extra value without contradicting 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 compact and well-structured: a single-sentence purpose, a bulleted list of use cases, and a final sentence on return values. Every section adds value and there is no redundant or verbose phrasing.

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 tool's simplicity (one required parameter), extensive annotations, and presence of an output schema, the description adequately covers purpose, usage, and return content. It does not exhaustively describe edge cases, but that is not necessary given the schema and annotation richness.

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 input schema fully documents the only parameter, rxcui, with a description ('RxCUI of the drug') and a regex pattern. The description does not add additional semantics beyond restating that the tool operates on a drug. With 100% schema coverage, a baseline score of 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 opens with a specific verb and resource, 'Get therapeutic and pharmacologic classes for a drug,' and includes concrete examples ('Beta-blockers', 'NSAIDs'). This clearly distinguishes it from sibling tools like rxnorm_search or rxnorm_ingredients by focusing on classification.

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 'Use this tool to' section provides explicit use cases: finding drug class, therapeutic categories, and mechanism of action classifications. This gives clear context for invocation, though it does not explicitly name alternative tools or state exclusions, so it lacks the full 'when-not-to-use' guidance.

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