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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the bar is lower. The description adds useful context about the kind of data returned (synonyms, status, related concepts) but does not disclose additional behavioral traits such as error handling or response shape, which is acceptable given the output schema and annotations.

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 tight and front-loaded: the main action is in the first sentence, followed by compact bulleted uses and an example. Every sentence earns its place with no redundant content.

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?

Given the existing output schema, annotations, and 100% schema parameter coverage, the description covers purpose, use cases, and an example format. A small gap is the lack of explicit routing guidance relative to sibling search tools, but overall the context is sufficient for correct invocation.

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 the baseline is 3. The description adds an example RxCUI ('161') but does not meaningfully enrich the parameter semantics beyond what the schema already documents for rxcui and include_related.

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 opens with a specific verb and resource: 'Get detailed information about a specific RxNorm concept by RxCUI.' The bulleted list further clarifies the exact value (name, synonyms, status, related concepts). This clearly distinguishes it from sibling tools like rxnorm_search (search by name) and rxnorm_ingredients (list 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 description provides explicit 'Use this tool to' bullets, giving an agent clear scenarios for invocation. However, it does not explicitly name alternatives or state when not to use this tool, which would be helpful given the many overlapping RxNorm sibling tools.

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