get_drug

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

No annotations, but description lists return content (names, dosage forms, NDC codes, label sections). Adequately discloses output without contradicting any 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?

Four sentences with no extraneous content; purpose, returns, usage guidance, and parameter details are front-loaded and concise.

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 tool simplicity (one param, output schema exists), description covers purpose, input semantics, and procedure to obtain RxCUI. No gaps for this use case.

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 coverage is 0%, but description fully explains the 'rxcui' parameter with definition and example, adding significant semantic value beyond the schema.

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 it gets the full profile for a drug by its RxCUI. It distinguishes from siblings like search_drugs (for name search) and get_drug_by_ndc (by NDC).

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?

Explicitly advises to use search_drugs first if only a name is available, providing clear context. Does not explicitly exclude other siblings but the narrow scope makes it appropriate.

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