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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: the data source (openFDA), the output shape ('clean structured text'), and a 'Not medical advice' disclaimer. It does not mention coverage limits, freshness, or error/not-found behavior, so not a 5.

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 front-loaded sentence that packs the resource, the returned fields, the source, and the disclaimer with essentially no filler. It is dense but every clause carries information; the only minor cost is that one long list-heavy sentence is slightly harder to scan than segmented phrasing.

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?

Output schema exists, so return values need not be explained, and the annotations carry the safety profile; combined with a single fully documented required parameter, an agent has what it needs to call this correctly. The description also covers source and the medical-advice caveat. Only minor disambiguation against the drug-safety siblings is missing.

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 the single parameter is already documented as 'Drug brand or generic name'. The description's mention of 'brand and generic names' and 'any drug' restates rather than extends that, so the baseline 3 for full schema coverage applies.

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+resource ('FDA drug label lookup') and enumerates the exact content returned: boxed warning, indications, contraindications, warnings, interactions, brand/generic names, manufacturer, route. This distinguishes it implicitly from drug-safety siblings like get_drug_safety and detect_drug_safety_signals, since it retrieves the regulatory label rather than signal/metric data. It never names those siblings explicitly, so it falls short of a 5.

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?

'for any drug' establishes scope but no when-to-use guidance, no exclusions, and no reference to the closely related get_drug_safety / detect_drug_safety_signals / list_drug_approvals siblings an agent must choose between. Usage is left to inference from the field list.

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