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

There are no annotations, so the description itself must convey the operation's behavior. It does indicate a read-style exact lookup by identifier and mentions the three accepted identifier forms. However, it does not disclose return format, not-found behavior, or whether the identifier matching is exact/case-insensitive, leaving some behavioral ambiguity.

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 very compact: a single English sentence and its Chinese equivalent. It front-loads the core operation and key identifier variants, though the bilingual duplication is somewhat redundant.

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 simple one-parameter lookup, the description is mostly adequate, but it omits return-value details, error/not-found handling, and any rationale for when to use this versus related get/list/resolve tools. Since there is no output schema and no annotations, a bit more contextual guidance would improve completeness.

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 only provides the parameter name 'name' with no description, so the schema offers almost no semantic value. The description compensates meaningfully by explaining that the single parameter can accept a haplogroup name, hid, or SNP, which is essential for correct invocation.

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 the operation ('Get'), the resource ('a single haplogroup'), and the accepted lookup keys ('name / hid / SNP'). It distinguishes itself from list/tree siblings by emphasizing 'single', though it does not explicitly contrast with get_haplogroup_lineage or get_haplogroup_mutations.

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?

There is no guidance about when to choose this tool over the many siblings such as list_haplogroups, children_haplogroups, subtree_haplogroups, resolve_snp, or get_haplogroup_lineage. The word 'single' implies exact lookup, but no when-to-use or when-not-to-use conditions are stated.

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