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

readOnlyHint=true already tells the agent this is a safe read, so the description's extra value is the note that results are grouped by concept type and span all term types. It says nothing about result volume, pagination, or the shape of failure (e.g., no match), which limits its added context.

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 behavior front-loaded and no padding; the trailing endpoint reference is minor filler but doesn't dilute the payload.

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 two-parameter, fully documented read tool with no output schema, the description supplies the essential scope (all term types, grouped by concept type). Only pagination/result-size behavior is left unstated, which is a small gap.

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 'name' and 'expand' are already documented with examples ('prednisone', 'psn'). The description adds nothing to parameter meaning, 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 (search) and resource (drug products, all term types) and notes the grouping by concept type. It implicitly distinguishes itself from the sibling rxnorm_find_rxcui_by_name (broad term-type search vs. single RxCUI resolution), though no sibling is named 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?

The description says what it searches but gives no when-to-use guidance, no exclusions, and never routes the agent to alternatives such as rxnorm_find_rxcui_by_name or rxnorm_get_approximate_match, despite those being close neighbors.

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