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

Annotations already establish this as a safe, idempotent, closed-world read, so the description's job is lighter and it does add value: "Retrieve the relevant record before making substantive claims" signals that results are references/snippets requiring a follow-up fetch via get_overview rather than being authoritative on their own. It does not discuss result volume or how limit behaves, but that is largely covered by the schema.

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?

Four short sentences, front-loaded with the scope statement before the routing advice and the safety exclusions. Every sentence carries a distinct instruction; there is no filler, though the exclusion clause is slightly redundant in mentioning both "personal dosing" and "individual medication assessments."

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 an output schema present, return values need no explanation, and the safety profile is covered by annotations. The description adequately covers scope, query style, routing, and a follow-up-retrieval norm; the only real omission is the semantics of the limit and types parameters.

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%, so the description must carry the load. It does add meaning for query ("Use public research terms") and effectively names the seven values of the types enum through the overview categories listed, but it never explains limit or its default/maximum, nor that types acts as a filter. Partial compensation only.

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 opens with a specific verb ("Search") and a precise resource set ("published Blossom topic, compound, safety, dosing, country, regional and clinical guideline overviews"), which maps directly onto the overview content types. An agent can distinguish this from search_papers or search_trials by the enumerated report types, though the description never explicitly contrasts itself with those siblings.

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?

It gives a query-phrasing rule ("Use public research terms"), a routing preference ("For general research on medication interactions, search compoundReport overviews first"), and explicit exclusions ("Do not use this tool for personal dosing or individual medication assessments, or ask for personal health details"). The exclusions are strong but never point to the tool that should handle those cases, leaving the agent to guess the alternative.

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