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

readOnlyHint=true already establishes a safe read, and the description confirms it is a name-based lookup via the RxClass endpoint, adding modest context. It says nothing about rate limits, result shape, or whether relas/relaSource change the output set, which is where real behavioral value would lie.

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?

Front-loaded with the core action, followed by the API provenance in a compact second sentence. The 'RxClass API' plus 'GET /rxclass/class/byDrugName' partly restate the same fact, a minor redundancy.

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 read-only lookup with a fully documented schema and readOnlyHint, the essential call information is present. However, nothing explains how relas/relaSource filter the returned class set or what the result resembles, leaving a moderate gap for an agent selecting among the many rxnorm siblings.

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%, so drugName, relas, and relaSource are already documented in the schema, including examples. The description adds no syntax or default behaviour beyond repeating that lookup is by drug name, so the baseline 3 applies.

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 a specific verb and resource: get the drug classes that contain a drug, with the lookup key (drug name) and the backing API (RxClass). It is clearly distinguishable from general concept lookups, but it does not explicitly differentiate from the inverse sibling rxnorm_get_class_members (get members of a class), which is the likeliest confusion.

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?

There is no when-to-use guidance, no mention of when to pick this over rxnorm_get_class_members (the inverse direction) or rxnorm_get_all_related, and no prerequisites or exclusions. Usage is only implied by the resource name.

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