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

With no annotations provided, the description carries full burden. It discloses the data source, filterable fields, and return types (NDA/BLA/supplemental). However, it does not mention pagination behavior (skip, limit) or rate limits. Overall, it provides decent transparency for a read-oriented search 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?

The description is two sentences long with no redundant words. It front-loads the action ('Search FDA drug approvals'), then enumerates filters and return fields efficiently. 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 7 parameters and no output schema, the description covers main filters and returns but omits pagination details, default ordering, and handling of empty results. It is adequate for a straightforward search but lacks completeness for edge cases.

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 description lists filter criteria (sponsor, brand, generic, date range) which adds context to the schema's parameters. However, 57% schema coverage means some parameters (skip, limit) are not described in the schema or the narrative. The description complements but does not fully compensate for missing parameter details.

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 FDA drug approvals from Drugs@FDA, lists specific filter criteria (sponsor, brand, generic, date range), and specifies return fields (application number, sponsor, names, approval date). It clearly differs from sibling tools (adverse events, labels, recalls) by focusing solely on approvals.

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 searching approvals but does not explicitly state when to use this tool over siblings (e.g., fda_adverse_events, fda_drug_label). No direct comparison or exclusions are provided, leaving the agent to infer from context.

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