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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the algorithmic basis (Poland–Scheraga / DECIPHER) and the shape of the computed result, but says nothing about cost of the temperature grid, runtime, or limits — modest added value against a low annotation bar.

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?

One tightly packed sentence that front-loads the resource and method before enumerating outputs. Dense nominal phrasing ('the cooperatively-melting domains behind each HRM peak') but no wasted sentences.

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, yet the description still summarises them usefully; parameters are fully documented in the schema. What remains missing is operational context — when this is preferred over the related melting/HRM siblings — so it falls short of complete.

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%, with ions, step, min_temp, max_temp, region_start/end and the _subject/_files selectors each documented inline. The description adds no parameter meaning at all, so the baseline 3 for fully-covered schemas 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 and resource: DNA melting behaviour computed by the Poland–Scheraga model (DECIPHER), returning a melt curve, Tm50, and cooperatively-melting domains per HRM peak. That output signature implicitly separates it from the sibling melting_temperature (single Tm) and analyze_melt_curves, though it never names an alternative outright.

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?

No when-to-use guidance is given, and no sibling is named or excluded. An agent cannot tell from the text whether melt_profile supersedes melting_temperature, feeds analyze_melt_curves, or is the right call for a plain Tm query.

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