query_pharmgkb

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

No annotations are provided, and the description does not disclose limitations, data freshness, authentication needs, or error handling. It only states what it shows, lacking behavioral context beyond the basic operation.

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 sentences, 16 words, front-loading the key purpose. Every word adds value; no redundancy.

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?

The description lists the types of data returned (drug-gene interactions, dosing guidelines, clinical annotations), which is sufficient for a single-parameter lookup tool. Lacks mention of failure modes or data format, but overall adequate.

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 describes 'rsid' as 'dbSNP rsID', and the description adds context by referring to 'variant', but adds no new technical detail beyond what the schema already provides. Schema coverage is 100%.

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 'Look up PharmGKB pharmacogenomic annotations for a variant' with specific examples of content (drug-gene interactions, dosing guidelines, clinical annotations), distinguishing it from sibling tools like query_clinvar or query_snpedia.

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 implies use when pharmacogenomic data for a variant is needed, but provides no explicit guidance on when not to use it or how it compares to alternatives (e.g., query_snpedia, query_clinvar).

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