calculate_hydrate_inhibitor

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

No annotations are provided, so the description carries full burden. It mentions the method (Hammerschmidt equation) but does not disclose what the output represents (e.g., rate in what units), whether it is a single value or multiple, or any side effects. The description lacks critical behavioral context.

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 with a single sentence stating purpose followed by parameter explanations. It is front-loaded and easy to scan. However, it could be slightly more structured (e.g., using bullet points for parameters), but overall it is efficient.

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?

Despite having an output schema, the description does not mention the output or its meaning. For a calculation tool, knowing the result format and units is important. Additionally, it lacks assumptions (e.g., gas gravity, pressure) or range constraints on inputs, leaving the tool partially incomplete.

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 input schema has 0% description coverage, so the description must add meaning. It provides clear explanations for three parameters (hydrate_temp_f, operating_temp_f, water_rate_bwpd) and lists valid values for the inhibitor parameter. This adds significant value beyond the schema's 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 it calculates hydrate inhibitor injection rate using the Hammerschmidt equation, and specifies supported inhibitors (methanol, MEG, ethanol). The verb 'calculate' and resource 'hydrate inhibitor injection rate' are specific. While sibling tools exist for other calculations, this one is distinct enough in its purpose.

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 implies usage when hydrate inhibitor injection rate needs to be computed, and lists supported inhibitors. However, it does not explicitly state when to use this tool versus alternatives (e.g., calculate_hydrate_temp), nor does it provide conditions where it should not be used. The guidance is implied but not explicit.

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