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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: a source link for every section, per-row list caps, and an explicit price of $0.004 per drug-query. It stops short of describing behavior for unknown or ambiguous drug names.

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 core capability is front-loaded in the first sentence, with cost placed last where it belongs. The clause "Built for AI agents and people in pharma, health tech, pharmacy, compliance and investing" is marketing padding that does not help an agent decide or invoke.

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?

With no output schema, the description must enumerate what comes back, and it does: five named sections, each with a source link, plus counts for FAERS reactions and ordering/newest-first conventions for lists. Combined with full schema coverage and read-only annotations, an agent has enough to call this correctly.

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 all three parameters are documented in-schema, so baseline is 3. The description reinforces the single-drug-name input and the section grouping that mode selects, but adds no semantics for the non-dossier mode values or for how maxItems interacts with per-section caps beyond what the schema states.

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 states a concrete capability with named sections: FDA boxed warning and indications, top FAERS adverse reactions with counts, US recalls and shortages, EU authorisation/EPAR and EU shortages, for a single drug name. That is far more specific than the title alone. It does not, however, distinguish itself from the sibling product_recalls, which plausibly overlaps on the recalls portion.

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 by "in one call" and the default dossier mode filling all five sections, which suggests using this tool for a combined safety/regulatory snapshot. There is no explicit statement of when to prefer it over product_recalls or when a narrower single-section call is appropriate, and no stated prerequisites or failure conditions.

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