get_mappings_by_rxcui

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves mappings but gives no information about the format of the response, potential rate limits, error conditions, or whether it's a read-only operation. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. There is no wasted verbiage or structural fluff.

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 lack of annotations and output schema, the description is insufficient for a tool that likely returns complex mapping data. It doesn't explain what 'mappings' entail (e.g., cross-references to other drug identifiers), the response structure, or any behavioral traits like pagination or error handling. This leaves the agent with inadequate context for reliable use.

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?

The input schema has 100% description coverage, with the 'rxcui' parameter clearly documented as 'The RxCUI to get mappings for'. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints on valid RxCUI formats. This meets the baseline for high schema coverage but doesn't enhance parameter understanding.

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 the action ('Get mappings') and the target resource ('for a specific RxCUI'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_all_rxcuis' or 'search_by_rxnorm_mapping' by focusing on mappings for a single identifier. However, it doesn't specify what type of mappings (e.g., to other drug codes) are retrieved, leaving some ambiguity.

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 no guidance on when to use this tool versus alternatives. With many sibling tools available (e.g., 'get_rxnorm_mappings_by_pharmacologic_class', 'search_by_rxnorm_mapping'), there is no indication of prerequisites, typical use cases, or exclusions. The agent must infer usage from the tool name alone.

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