get_drug_ingredients

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

With no annotations, the description carries the full burden. It does disclose what is returned (ingredient information, strength, dosage form), which is useful context, but it says nothing about behavior on an unknown drug, whether the lookup is case-sensitive, or whether RxCUI and name inputs behave differently. Adequate but thin for a zero-annotation tool.

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 tight sentences: the first front-loads the action and accepted identifier, the second adds the return contents. No filler or redundancy.

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-parameter lookup with no output schema, the description covers both the input form and the shape of the result, which is most of what an agent needs. A brief note on no-match behavior would complete 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 schema already documents drug_identifier as accepting 'Drug name (brand or generic) or RxCUI'. The description restates the same accepted input forms without adding format, casing, or disambiguation rules, so baseline 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+resource: 'Get active ingredients for a given drug name or RxCUI', which is clearly distinct from the resources handled by siblings like get_generic_name or get_atc_classification. It never explicitly names a sibling or routing condition, so it stops short of the 5 bar.

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?

Usage is implied — an agent needing ingredient composition would naturally reach for this tool — but the description gives no explicit when/when-not guidance and never references the sibling tools (get_generic_name, get_brand_names) that sound superficially related. No prerequisites or lookup-failure behavior is mentioned.

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