rxnorm_classes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, indicating a safe, non-destructive operation. The description adds value by detailing the return content: 'class IDs, names, and classification sources', which goes beyond the annotations. No behavioral traits are contradicted or omitted.

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 concise, consisting of a lead sentence, bulleted use cases, and a concluding line about return values. Every sentence adds value without redundancy. Front-loaded with the main action.

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 that an output schema exists, the description does not need to fully explain return values, but it still mentions the key fields (class IDs, names, sources). The tool has a single required parameter and a clear purpose; the description covers all necessary context for an agent to use it correctly.

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 has one parameter 'rxcui' with a regex pattern and a description already provided. Schema description coverage is 100%. The tool description does not add any additional meaning or context for the parameter, such as explaining what an RXCUI is or how to obtain one. Baseline score of 3 is appropriate as the schema adequately describes the 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?

The description clearly states the tool retrieves therapeutic and pharmacologic classes for a drug, using a specific verb 'Get' and resource 'classes'. Among the numerous sibling tools, including other rxnorm_* tools, this description uniquely identifies its purpose, distinguishing it from rxnorm_concept, rxnorm_ingredients, etc.

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 clear contexts for use: 'Find the drug class', 'Identify therapeutic categories', 'Look up mechanism of action classifications'. It implies when to use this tool but does not explicitly state when not to use it or mention alternative tools. The sibling list is vast, so some explicit guidance would be helpful, but the given use cases are sufficient.

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