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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the underlying REST endpoint (GET /rxclass/classMembers) but nothing behavioral — no pagination, response shape, transitive-vs-direct behavior, or source-specific caveats beyond what the schema's 'trans' and 'rela' descriptions already say.

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?

Two short sentences with the core purpose front-loaded. The second sentence naming the RxClass API and REST endpoint earns marginal value for developers but is essentially reference trivia for an agent, keeping it just short of a 5.

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 read-only 5-parameter lookup with fully documented schema and readOnlyHint, the safety and input side is covered. But with no output schema, the description does not indicate what members look like (concepts, RxCUIs, names) nor how to obtain a classId, leaving modest gaps.

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%, so all five parameters (rela, ttys, trans, classId, relaSource) are already documented with examples and enum meaning. The description adds nothing over the schema, so the baseline of 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+resource: retrieving the drugs that belong to a given drug class, and grounds it in the RxClass API. This distinguishes it from siblings like rxnorm_get_drug_classes (list classes) and rxnorm_get_drugs (look up drugs by name), though it never names those siblings explicitly.

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 the prerequisite of obtaining a classId first, and no routing to alternatives. The only hint is the required classId parameter in the schema, which the description does not build on.

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