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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so safety is covered. The description usefully discloses the underlying algorithm (Poland–Scheraga via DECIPHER), which tells an agent what model assumptions underlie the numbers. It adds nothing about cost, ion-correction caveats, or limits, though the schema covers the cost note for `step`.

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?

A single front-loaded sentence that states method, then outputs in a natural reading order. Dense but free of filler; the HRM-peak clause is slightly jargon-heavy for an agent without domain context but still informative.

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 the description only needs to frame what comes back, which it does (curve, Tm50, domains). All eight parameters are schema-documented, nothing is required, and the model is identified. The only gap is a pointer to the sibling tools for simpler Tm queries.

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 the nested `_subject`/`_files` shapes are documented inline, so the schema carries the parameter burden. The description adds no parameter-level guidance (e.g. how min_temp/max_temp relate to the reported Tm50 or how region_start/end scope the melt), so the baseline of 3 applies.

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 names a specific computation (DNA melting profile, Poland–Scheraga/DECIPHER) and enumerates its outputs: melt curve of mean helicity vs temperature, Tm50, and cooperatively-melting domains per HRM peak. It is clearly not a generic melting-temperature lookup. However, it never names or contrasts the obvious siblings (melting_temperature, analyze_melt_curves), so full sibling differentiation is missing.

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 by the output description – an agent can infer this is the tool for a full melt curve plus HRM domain decomposition – but there is no explicit when-to-use, when-not-to-use, or pointer to melting_temperature/analyze_melt_curves as alternatives. Nothing is misleading, but the routing work is left to inference.

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