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

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower. The description adds only the underlying REST route (GET /rxcui), which is traceability rather than behavior; it says nothing about result cardinality, ambiguity handling, or how multiple matches are ordered.

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 sentences, zero padding, with the core purpose front-loaded before the API reference. Nothing needs to be trimmed.

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 single-lookup tool with full schema coverage and a readOnlyHint, the definition covers what an agent needs to call it. No output schema exists, so return format need not be explained, though a note on how ambiguous name matches are returned would have completed it.

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% and the enums for 'allsrc' and 'search' are fully documented in the schema, including defaults. The description adds no additional parameter meaning, so the baseline of 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 and resource ('Find RxNorm concept IDs (RxCUIs) matching a drug name string'), so the agent knows exactly what it returns. It does not, however, distinguish itself from the sibling rxnorm_get_approximate_match, which overlaps on the name-lookup use case.

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 guidance on when to use this versus alternatives such as rxnorm_get_approximate_match or rxnorm_get_spelling_suggestions, nor on when the exact/normalized/approximate modes should be selected. Usage must be inferred entirely from the name.

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