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

The readOnlyHint annotation already establishes this is a safe read. The description adds useful context by listing what a record contains and naming the underlying openFDA data source, but says nothing about result limits, pagination semantics, or rate limiting beyond what the schema already conveys.

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?

Two compact sentences, front-loaded with the verb and dataset, with the field enumeration and data source appended. No wasted prose, though the field list is somewhat dense.

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 compensates by enumerating the fields a record contains. Annotations cover the safety profile and the schema fully documents parameters, so the agent has enough to call it correctly; only usage routing remains thin.

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 coverage is 100%, so all four parameters (skip, sort, limit, search) are fully documented in the schema. The description adds no parameter-level detail, so baseline 3 is appropriate.

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 (Search) and resource (the National Drug Code directory) and enumerates the exact fields of the dataset (code, name, dosage form, route, active ingredients, marketing status, labeler). This clearly differentiates it from the many sibling search_* tools targeting drug events, labels, recalls, drugsfda, etc.

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 says what the tool searches but never says when to choose it over the numerous sibling tools (e.g., search_drug_labels vs search_drugsfda vs search_drug_ndc). No alternatives, no conditions, no prerequisites are given.

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