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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered externally. The description adds only the list of searchable facets and says nothing beyond annotations about pagination via cursor, the limit ceiling, or the fact that results come from multiple heterogeneous source datasets.

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 with no padding; the facet list is the useful content and it reads cleanly. It is arguably too terse for a 15-parameter tool, but that is a completeness issue rather than verbosity.

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 15-parameter, zero-coverage, no-output-schema search tool, one sentence is not enough. Missing are filter-combination semantics, pagination behavior, the meaning of source and limit, and any indication of result shape or ordering.

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 0% across 15 parameters, so the description must carry the explanatory burden. It names roughly seven fields (brand, generic, ingredient, manufacturer, dosage form, route, free text) but leaves ndc, rxcui, spl_set_id, dea_schedule, shortage_status, source, limit, and cursor entirely unexplained, including which field 'free text' maps to.

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 gives a specific verb ('Search') and resource ('drug products') and enumerates the facets that can be matched, so the agent knows exactly what class of operation this is. It does not explicitly contrast with the sibling drugs_get, so the distinction between searching and fetching a known drug is left implicit.

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?

There is no guidance on when to use this instead of drugs_get, no note on whether multiple filters are ANDed, and no mention of when to page with cursor. The agent is told what can be searched but not when this search is the right choice over the retrieval sibling.

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