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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the bar is lower. The description adds genuinely new behavioral context not present in structured fields: a free daily allowance and a $0.001 USDC per-call charge via x402, which tells the agent there is a cost/quota dimension to invoking it.

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 no filler; the functional statement is front-loaded and the pricing caveat follows. Nothing reads as redundant.

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?

An output schema exists, so return-format explanation is not required, and the tool is a simple single-input lookup. The description covers purpose and cost, but omits what happens on no-match and how many suggestions are returned, which is a minor gap for the agent.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'name' as the drug name as typed. The description adds no further semantic detail (e.g. formatting, case sensitivity, multi-word handling), 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?

The first sentence states a specific resource and outcome: correctly spelled RxNorm drug names near the input, which is enough for an agent to know this is a spelling-correction/lookup tool. It does not, however, distinguish itself from the close sibling rxnorm__approximate, which plausibly overlaps in intent.

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 prefer this tool over rxnorm__approximate or other RxNorm siblings, nor any condition for use (e.g. misspelled input). The only contextual note is commercial (pricing), not usage guidance.

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