calculate_brine_pvt

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

The description mentions the correlations used (McCain 1990, Osif 1988) and the default salinity, which provides some transparency. However, it does not disclose validity ranges for temperature, pressure, or salinity, nor any limitations. Given no annotations, the description carries the full burden but still leaves gaps.

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 well-structured, with a brief summary followed by a bullet list of returned properties and parameter descriptions. Every sentence adds value and there is no extraneous text.

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?

For a tool with 3 parameters and an output schema, the description covers the key aspects: purpose, parameters, return values, and correlations. It lacks usage guidance and validity ranges but is otherwise adequate. The presence of an output schema reduces the need to detail return structure.

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?

With 0% schema description coverage, the description compensates by explaining each parameter's units (F, psi, ppm) and default value (salinity=0). This adds essential meaning beyond the schema types. However, it could include typical ranges or constraints for better usability.

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 that the tool calculates brine/formation water PVT properties and lists the specific outputs (density, viscosity, FVF, compressibility). It distinguishes itself from the sibling 'calculate_pvt_properties' by specifying the fluid type, making the purpose unambiguous.

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 explicit guidance is provided on when to use this tool versus alternatives such as 'calculate_pvt_properties' or other PVT-related tools. The description assumes the user already knows to use this for brine water, but does not contrast or state exclusions.

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