search_fda_orange_book

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

With no annotations provided, the description carries full transparency burden. It discloses that data is downloaded from FDA bulk files and cached for 24 hours, indicating data freshness. It does not mention destructive actions, authentication, or rate limits, but overall it gives a good behavioral overview. No contradiction with annotations (none exist).

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 three sentences with no wasted words. It front-loads the core purpose, lists searchable parameters, mentions return values, and notes data caching. Every sentence adds value.

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 tool has 6 parameters, no required ones, and no output schema, the description covers usage, return content, and data source. It could include pagination behavior or error handling hints, but for a search tool it is reasonably complete.

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 covers all 6 parameters with descriptions, so schema_description_coverage is 100%. The description reiterates the main searchable fields but adds no additional detail beyond what the schema provides. Baseline 3 is appropriate because the schema does the heavy lifting.

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 searches the FDA Orange Book for approved drug products with therapeutic equivalence evaluations. It lists specific searchable fields (trade name, ingredient, applicant, application number, TE code) and mentions the return type (product details, patent counts, exclusivity counts). This distinguishes it from sibling tools like search_fda_purple_book (biological products) and others.

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 finding drugs by various identifiers but does not explicitly state when not to use it or provide alternatives among the many sibling drug search tools. It lacks exclusion criteria, though the context is clear for Orange Book data. The description could guide agents away from using this for adverse events or recalls.

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