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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful behavioral context: partial-name matching and the specific DRUG-level fields returned (RxCUI/NDC, schedule, controlled flag, strength, form).

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?

Three tight sentences, front-loaded with the core action and search modes, with return shape and drill-down guidance following. No wasted text.

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 carries the return-value burden and does name the key returned fields and concept granularity. Coverage is good for a 4-param search tool, though return-value completeness (e.g. pagination behavior) is only partially addressed.

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%, so the schema already documents all four parameters including the code formats and pagination cursor/size. The description restates the name and code formats but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ("Search Photon's medication database") and explicitly lists the two lookup modes (partial drug name, or code via RxCUI/NDC/SKU). It further distinguishes itself from siblings by noting it returns DRUG-level concepts and pointing to list_medication_products / list_medication_packages for drill-down.

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 routes the agent clearly: use this for drug-level concepts and drill down with the named sibling tools. The alternatives are named and the selecting condition (DRUG-level vs product/package level) is stated, though it doesn't spell out explicit when-not scenarios.

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