lookup_drugsfda_application

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('fetch') and does not disclose potential error behavior, read-only nature explicitly, rate limits, or what happens when the application number is invalid. The parameter description note about prefix matching provides some behavioral context, but that resides in the schema, not the tool description.

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, tightly-worded sentence with no filler. It front-loads the core function immediately and uses precise terminology.

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 simple read-only lookup tool with one well-documented parameter and a defined output schema, the description provides the essential information needed to select and use the tool. It could mention error cases, but these are likely covered by the output schema. Overall complete enough for its simplicity.

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 provides 100% description coverage for the single parameter, including detailed format instructions (prefix required, case-insensitive). The tool description adds nothing beyond naming the parameter type (NDA/BLA/ANDA), which is already in the schema. Baseline 3 is appropriate.

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 tool's function with a specific verb ('Fetch') and resource ('Drugs@FDA application metadata') and specifies the input type (NDA/BLA/ANDA). It distinguishes from sibling device lookup tools by naming Drugs@FDA and drug application numbers.

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 explicit guidance on when to use this tool versus alternatives or any exclusions. It implies usage for fetching drug application metadata, but does not mention sibling tools or when not to use it. This is minimal/no guidance beyond the obvious.

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