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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered. The description adds no behavioral context beyond that — it says nothing about snapshot retention semantics, error behavior for unknown RxCUIs, or what 'clinical drug' resolves to.

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?

A single short fragment with zero filler and the key input front-loaded. It is efficient, though being a sentence fragment rather than a complete statement slightly undercuts clarity.

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?

This is a simple two-parameter read tool with full schema coverage, so little is required. But with no output schema, the description should explain the return value more precisely than the vague 'clinical drug', and it omits the snapshot behavior of as_of entirely.

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, as_of) are documented in the schema, which sets the baseline at 3. The description adds no extra meaning about format or the snapshot semantics of as_of, so it neither compensates nor detracts.

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 phrase names the resource being returned ('the clinical drug') and its key input ('an RxCUI'), so an agent can infer a mapping lookup. However, it is a bare noun phrase with no verb and it does not distinguish itself from near-identical siblings like get_drug or lookup_ndc, leaving the exact operation ambiguous.

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 statement of when to use this tool versus get_drug, lookup_ndc, or search_medications, and no mention of prerequisites or the snapshot behavior implied by as_of. The agent must guess which of the several lookup tools is correct.

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