rxnorm_search

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is safe and idempotent. The description adds that results include identifiers, names, and term types, but does not discuss behavior like case sensitivity, wildcard support, or the implications of openWorldHint. No contradictions with annotations.

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?

The description is reasonably concise with a clear structure: a general purpose sentence followed by bullet points. However, some redundancy exists (e.g., 'Search for drugs' in the first line is repeated by the bullet 'Find drug concepts'). Could be slightly tighter.

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?

Given the presence of an output schema, the description need not fully document return values, but it mentions key fields. However, it does not address behavior like exact vs. fuzzy matching, case sensitivity, or how the results are ordered. For a search tool with many siblings, this is adequate but not complete.

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?

The input schema has 100% description coverage, with both 'query' and 'max_results' already documented. The description merely restates these (e.g., 'Drug name to search (brand or generic)') without adding new meaning or constraints beyond the schema.

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 clearly states 'Search for drugs in RxNorm' and lists specific use cases (find drug concepts, look up medications, search formulations). It also notes the output includes RxCUI identifiers, names, and term types. However, it does not explicitly distinguish from sibling tools like 'rxnorm_concept' or 'rxnorm_ndc', which reduces specificity.

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 provides bullet points on when to use the tool (find drug concepts, look up medications, search formulations). However, it does not mention when not to use it or provide alternatives among the many sibling tools, leaving the agent without clear exclusion criteria.

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