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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing the data source (RxNorm/NLM), that it returns RxCUI codes, that combination products are included, that UK-only brands are excluded, that it does not indicate which brands are currently marketed, and that it costs 1 credit. These are exactly the caveats an agent needs before relying on results.

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?

Purpose is front-loaded in the first sentence, with scope limits and cost after it, so an agent can stop reading early if it only needs the purpose. It is dense but not padded, though the 'travellers, carers' audience sentence is the weakest link and could be trimmed.

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 single-parameter lookup with no output schema, the description covers what comes back (brand names with RxCUI codes), where it comes from, and the three limitations that would otherwise cause misevaluation (US-only, combination products included, no marketing-status signal). Nothing material 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 there is only one parameter, so the schema already documents 'generic'. The description reinforces its meaning indirectly by showing a generic name example and noting that combination products containing the ingredient are included, but adds no format or normalization guidance (e.g. spelling tolerance, case) beyond the schema. Baseline 3 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?

The description opens with a direct question that names the exact output ('What brand names is this drug sold under?') and follows with a concrete verb+resource statement plus a worked example (simvastatin: Zocor, Vytorin, Flolipid). It is clearly distinguishable from siblings like drug_generic_ingredient and drug_name_match, which go in the opposite direction or perform matching.

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 use context ('useful for travellers, carers and anyone comparing US and UK medicine names') and states the key scoping condition that the brands are US-only. It stops short of explicitly naming an alternative tool or saying when NOT to use it, so it falls just below the top score.

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