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

Annotations already establish this is a safe, non-destructive, closed-world read, so the description's job is to add behavioral context — and it does: it discloses that the tool aligns the two inputs, reports substitutions, indels and uncalled positions, maps them onto design features, and ranks by Ensembl consequence severity. What it does not say is anything about cost, runtime or sensitivity to the many alignment tuning sliders.

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?

Front-loaded with the core comparison and free of filler, though the two sentences are long and heavily clause-stacked. The severity-gating rationale at the end is useful but slightly promotional in tone.

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 13-parameter tool with a nested _subject object and an output schema, the description covers the input pairing, the analysis performed, and the ranking scheme, which is enough for correct invocation. It stops short of explaining how the advanced alignment sliders affect results or when to adjust them.

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% and every parameter is documented in-schema, including the design/result distinction, so the baseline applies. The description reinforces the semantics of the two required inputs (intended construct vs. sequenced result) but adds no information about the eleven alignment-limit sliders beyond what the schema already says.

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 and both operands — compare a sequencing RESULT against the designed construct — and names the outputs (what differs, where, what it lands in). It is distinguishable from bare alignment tools, but it never explicitly separates itself from nearby siblings such as compare_reads_to_reference or alignment_agreement, so an agent must infer the boundary.

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 implied rather than stated: the closing clause about a pipeline gating on 'nothing worse than synonymous' suggests the intended context, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many alignment/comparison siblings.

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