get_rxnorm_mappings_by_pharmacologic_class

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 describes a read operation ('Find') but does not cover aspects like rate limits, error handling, response format, or data scope (e.g., whether it returns all mappings or a subset). This leaves significant gaps in understanding how the tool behaves.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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 incomplete. It does not explain what the tool returns (e.g., format, structure of mappings) or behavioral traits like performance or limitations. For a tool with no structured support, more detail is needed to fully inform usage.

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 description mentions 'pharmacologic class SET ID', which aligns with the single parameter 'pharmaSetId' in the schema. Since schema description coverage is 100%, the schema already documents the parameter adequately. The description adds minimal value beyond the schema, meeting the baseline for high coverage.

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 ('Find RxNorm mappings') and the target ('drugs that belong to a specific pharmacologic class SET ID'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'get_pharmacologic_class_mappings_for_setid' or 'get_rxnorm_mappings_for_setid', which might have overlapping functionality, so it lacks full sibling distinction.

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, such as 'get_pharmacologic_class_mappings_for_setid' or 'search_drugs_by_pharmacologic_class'. It mentions the parameter but does not specify prerequisites, exclusions, or comparative contexts, leaving usage unclear.

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