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

Annotations already declare readOnlyHint and destructiveHint=false, so the description's job is to explain the computation, and it does: it discloses that each oligo is scored by best binding site, mismatch count, and 3′-end position, including the polymerase-extension rationale. It stops short of stating how ties or non-binding oligos are reported, but the core analytical behavior is transparent.

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?

It is a single front-loaded sentence that opens with the action and resource, then enumerates the three results. The colon-delimited list is efficient, with the only minor bloat being the explanatory 3′-end clause that could be tightened.

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 an output schema exists and all 8 parameters are described in the schema, the description only needs to frame what the analysis answers, which it does. Nothing essential for correct invocation is missing, though a note on which input sources sequences may come from would round it out.

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 parameters like three_prime_window, probes (no 3′ rule), and primers (IUPAC, name=SEQUENCE) are already fully documented in the schema. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline 3 when the schema does the heavy lifting.

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?

It states a specific verb (check) and resource (a published PCR or sequencing assay) and spells out what the analysis returns: best binding site per genome, mismatch count, and whether a mismatch falls in the extendable 3′ end. This is clearly distinguishable from design-oriented siblings, though it never names the close neighbours (check_primer_specificity, find_primer_snps, primer_check) it could be confused with.

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 phrase 'against the sequences that are circulating now' implies the use case (re-validating an existing published assay against current genomes), which is genuine usage context. However, there is no explicit when-to-use vs when-not, and no guidance on choosing this over check_primer_specificity or find_primer_snps, which an agent selecting among many primer-check tools would need.

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