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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds nothing further — it does not explain the historical as_of capability, whether a single result or a set is returned, or what happens on an unknown RxCUI.

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?

It is a single six-word fragment with zero waste and the key concept front-loaded, but the terseness comes at the cost of substance rather than being genuinely efficient. Not padded, but under-written.

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?

There is no output schema, so the description should say what a lookup yields (a name, a structured drug object, an error for unmapped codes). It says none of this, and given the time-travel parameter it also omits that historical answers are possible.

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 both parameters (rxcui format, as_of semantics) are already documented in the schema. The description adds no parameter meaning beyond that, 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?

"The clinical drug for an RxCUI" conveys the direction of the mapping (RxCUI in, drug out), which lightly distinguishes it from lookup_ndc. But it is a noun fragment with no verb and leaves "clinical drug" as unexplained domain jargon, so the purpose is only vaguely specified.

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?

No when-to-use guidance at all. With siblings like get_drug, lookup_ndc, and search_medications in the list, the description never states that this is the reverse index (identifier → drug) nor when to prefer it over a name-based search.

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