Genomic-Agent-Discovery

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

With no annotations provided, the description carries full burden and successfully discloses return structure ('chromosome, position, and the patient's alleles') with concrete examples ('AG', 'CC', 'TT'). However, it omits error handling (e.g., rsID not found behavior) and authorization requirements.

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 with zero waste: first states purpose, second discloses return format. Every word earns its place and the description is appropriately front-loaded.

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 tool without output schema, the description adequately compensates by detailing return values. Lacks only error-condition disclosure to be fully 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?

Schema coverage is 100% with the rsid parameter fully documented as 'dbSNP rsID, e.g. 'rs1234567''. The description adds no additional parameter semantics beyond the schema, meeting the baseline for high-coverage schemas.

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 specific action ('Look up'), resource ('patient's genotype'), and scope ('for a specific rsID'). The 'specific rsID' phrasing effectively distinguishes this from the sibling tool query_genotypes_batch.

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?

Implies singular use via 'specific rsID', but provides no explicit guidance on when to prefer query_genotypes_batch for multiple variants, nor any prerequisites for accessing patient genomic data.

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