Openfda Drug Label

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. 'Get' weakly implies a read-only lookup, but there is no mention of rate limits, API key requirements, or whether results are paginated or truncated; the section list is the only extra context offered, and an output schema already exists to cover returns.

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?

A single compact sentence with the core action front-loaded and no filler. It is appropriately sized for a one-parameter lookup, though the phrase 'information: indications, warnings, dosage, mechanism' is slightly list-heavy for a description whose return shape is governed by the output schema.

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 one-param lookup with a full output schema, the essentials of what is returned and what to pass are covered. What is missing is the guidance an agent actually needs to choose this tool over its FDA and drug siblings, which is the main open gap.

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% for the single drug_name parameter, including brand/generic and examples, so the schema does the heavy lifting. The description adds no format, casing, or synonym guidance beyond that, which is the expected baseline 3.

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 ('Get') and resource ('FDA drug label information') and enumerates the content covered (indications, warnings, dosage, mechanism). However, it never differentiates itself from close siblings like openfda_adverse_events, openfda_drug_enforcement, or drugbank_search, so an agent must infer which source fits the query.

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?

No when-to-use guidance, no exclusions, and no routing to alternatives. With three other drug-related tools in the sibling list, the description leaves entirely to inference whether label data, adverse events, enforcement reports, or DrugBank should be called.

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