water_saturation_temperature

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

With no annotations provided, the description carries the burden of behavioral disclosure. It correctly emphasizes absolute pressure over gauge, which is a key behavioral caveat. However, it does not mention any limitations such as temperature ranges, precision, or what the output looks like beyond the implicit calculation. The output schema may cover the return format, but the description itself is somewhat sparse on behavioral details.

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?

The description is concise and front-loaded with the main purpose. It uses a short example and a clear warning about gauge pressure, with no extraneous content. Every sentence serves a purpose, making it easy for an agent to quickly grasp what the tool does and how to use it correctly.

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?

The tool is simple, and the output schema likely defines the return value, so the description doesn't need to explain that. It covers the essential usage context: the pressure type and a common unit example. It could be slightly more complete by mentioning the range of pressures supported or any assumptions about water purity, but for a straightforward thermodynamic calculation, it is sufficiently 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?

The schema itself documents both parameters with types, defaults, and an enum for pressure_unit. Since schema description coverage is 0%, the description must add meaning beyond the schema. It does by explaining the absolute pressure requirement and providing the conversion factor for atm to kPa, which helps users correctly set the pressure parameter. This is meaningful value added beyond the structured 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?

The description states the specific verb 'Calculate' and the resource 'water's boiling/saturation temperature', and clearly specifies the input as absolute pressure. It provides a concrete example question and clarifies that standard atmosphere is 1 atm or 101.325 kPa absolute, leaving no ambiguity about the tool's function.

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 description explicitly says 'Use this for questions such as...' and gives a clear example. It also warns against using gauge pressure, which is a critical usage constraint. Although there are no sibling tools to differentiate from, the guidance is clear and actionable.

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