calculate_hydrate_temp

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

No annotations are present, so the description carries the full burden. It fails to disclose behavioral traits such as whether the calculation is deterministic, if it has side effects, or what assumptions/limitations apply (e.g., valid only for certain gas compositions or pressure ranges). Merely stating the method is insufficient.

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 extremely concise, consisting of a single purpose sentence followed by parameter documentation in a clear list format. No extraneous words, and the purpose is front-loaded. Every sentence adds essential information.

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?

While an output schema exists (so return values are covered), the description does not specify prerequisites, valid input ranges beyond gas_sg, or methodological assumptions. For a simple calculation tool, it is minimally adequate but leaves important context (e.g., pressure limits) unaddressed.

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 has 0% description coverage, but the description adds meaningful details: 'pressure_psi' is labeled as 'System pressure in psi', and 'gas_sg' is described as 'Gas specific gravity (air = 1.0, range 0.55-1.0)'. This provides units and a valid range for gas_sg, though pressure_psi lacks a range. The added semantics improve understanding beyond schema titles and types.

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 clearly states the verb 'Estimate' and the resource 'hydrate formation temperature' with a specific method ('gas-gravity method (Katz chart)'). The tool name itself is specific, and the description differentiates it from sibling tools like 'calculate_hydrate_inhibitor' by focusing on temperature estimation.

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 guidance is provided on when to use this tool versus alternatives such as 'calculate_hydrate_inhibitor' or under what conditions (e.g., pressure/temperature ranges) the method is applicable. The description only states what it does, without usage context or exclusions.

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