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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes beyond them by disclosing the underlying implementations (scikit-allel for the statistics, bcftools +fill-tags for the HWE test), the ploidy-2 assumption, and provenance via validation on 1000 Genomes phase 3 APOL1 across 32 groups. It stops short of stating performance/scale characteristics or output shape details, so it is useful added context rather than a complete behavioral profile.

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 core purpose and the full statistic inventory are front-loaded in one dense sentence, with a short second sentence for validation provenance. Every clause carries content, though the enumeration is long enough that key constraints (ploidy 2, group scoping) are buried mid-sentence rather than signposted.

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?

An output schema exists, so return values need not be explained, and the description still covers what is computed, the ploidy-2 expectation, and the all-samples-vs-one-group behavior. For a 6-parameter tool with nested objects it is nearly adequate; the missing piece is any guidance on choosing among the other population-genetics siblings.

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 baseline is 3. The description echoes the group semantics ('for all samples or one population') but adds no syntax or format detail beyond the schema, which already explains vcf, group, groupBy, and populations; no parameter meaning is enriched.

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+resource: per-site and per-sample genotype statistics computed from a call set, and enumerates the exact statistics produced (allele counts/frequencies, call rates, het/hom counts, Ho/He, F, HWE with excess-het tail). It never names or distinguishes itself from adjacent population tools such as population_fst, population_ancestry, linkage_disequilibrium, or variant_call_summary, so the sibling differentiation that would earn a 5 is absent.

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?

Usage is only implied: you supply a VCF call set and optionally restrict to one group's samples or supply a populations sample table. There is no explicit statement of when to reach for this tool rather than population_fst/ancestry/LD, nor any 'when not to use' or prerequisite guidance, and the scoping sentence 'for all samples or one population' is the only routing signal.

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