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

With no annotations, the description carries the full behavioral burden, and it delivers the methodologically critical disclosure that BUBBLE point is the saturation basis (not dew) for blended refrigerants, plus the EPA 608/A2L prerequisite and an expected output range. It still omits error behavior and output formatting details, so it is not complete.

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?

Short, front-loaded, and every fragment carries information: definition first, then safety prerequisite, then saturation methodology, then interpretation benchmark. Slightly clipped telegraphic phrasing 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?

No output schema and no annotations, so the description must cover everything; 'Subcooling in Fahrenheit' does imply the return unit, but the accepted refrigerant values and failure modes for an invalid refrigerant string are unspecified. Adequate for a simple calculator, but not fully self-contained.

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 0%, and the description supplies units for two of three parameters (psig, F), which the schema lacks. The third and most error-prone parameter, the free-text 'refrigerant' string, is never explained - no accepted naming format and no valid list - which is a real gap for a 0%-coverage schema.

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?

Names the exact quantity produced (subcooling in Fahrenheit) and both inputs with their units (head pressure in psig, liquid-line temperature in F). It is clearly distinct from the sibling 'superheat', though it never explicitly says so.

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 domain framing and the 'Typical TXV target: 8-12F' benchmark, which tells the agent how to interpret a result. However, there is no explicit when-to-use guidance relative to 'superheat' or 'pt_lookup', and no statement of preconditions beyond the certification note.

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