get_generic_name

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

No annotations are provided, so the description carries the full behavioral burden. It states the conversion but says nothing about whether the lookup hits a cache/database, what happens if the drug is not found, whether multiple generics can be returned, or the return format. This is a substantial gap for an unannotated lookup 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 short sentences with no waste, front-loading the operation. Slightly redundant since the second sentence largely restates the first.

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 lookup tool with no annotations and no output schema, the description should clarify edge cases (unknown identifiers, multiple matches) and return shape. It leaves return behavior entirely undefined, which is a significant shortfall given the absence of structured behavior signals.

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% – the drug_identifier parameter is already documented as accepting a drug name (brand or generic) or RxCUI. The description repeats the accepted input types without adding syntax, format, or validation details beyond the schema. Baseline 3 is correct.

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: converting a drug name or RxCUI into its generic name(s). The conversion direction is clear. Sibling differentiation is partial – get_brand_names is the inverse operation and is implied but not named.

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 implies usage for brand-to-generic conversion but gives no explicit when-to-use or when-not-to-use guidance and does not name the alternative tools (get_brand_names, search_drug_by_name) that overlap in scope.

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