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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context about return contents (RxCUI, names, term types) and the normalized-name scope, but does not go deeper into search matching behavior, limits, or ambiguity handling.

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?

The description is well-structured with a short opening line and bulleted use cases, making it scannable. Every sentence adds some value, though the bullet 'Look up medications for prescribing' is somewhat generic and overlaps with the first bullet.

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 simple two-parameter search tool with rich annotations and an output schema, the description covers purpose, use cases, and result contents. It is complete enough to call correctly, though it would benefit from a brief pointer to sibling tools for follow-up concept detail or NDC lookups.

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 query and max_results are already fully documented in the input schema. The description adds limited extra meaning for parameters, mostly reinforcing that query can be a brand or generic name. Baseline 3 is appropriate because the schema carries the weight.

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 description clearly states a specific verb and resource: 'Search for drugs in RxNorm' and explains the return payload (RxCUI identifiers, names, term types). It is not a tautology and is easy to understand, but it does not explicitly distinguish this tool from sibling tools like rxnorm_concept or rxnorm_ingredients.

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 'Use this tool to' section gives clear usage context: find drugs by brand/generic name, look up medications for prescribing, and search formulations. There are no explicit when-not-to-use instructions or named alternatives, but the intended scenarios are concrete enough for an agent to select this tool appropriately.

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