petropt/petro-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what properties are returned (density, viscosity, FVF, compressibility) and mentions the specific correlations used, which is helpful context. However, it doesn't mention computational characteristics, accuracy limitations, or whether this is a pure calculation versus a database lookup.

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 efficiently structured with a clear purpose statement, return values, and parameter explanations in a compact format. Every sentence earns its place, and the information is front-loaded with the most important details first.

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?

Given that an output schema exists (though not shown), the description doesn't need to explain return values. It covers the purpose, methods, and parameters well. The main gap is lack of differentiation from sibling tools, but for a calculation tool with good parameter documentation and output schema, this is reasonably 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?

With 0% schema description coverage, the description fully compensates by providing clear semantic meaning for all three parameters: temperature in F, pressure in psi, and salinity in ppm with default 0 meaning fresh water. This adds significant value beyond the bare schema, which only provides titles without units or context.

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 tool calculates brine/formation water PVT properties using specific correlations (McCain 1990 and Osif 1988), which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'calculate_pvt_properties' or 'calculate_gas_z', which appear to be related PVT calculations.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for PVT and fluid property calculations (e.g., calculate_pvt_properties, calculate_gas_z, calculate_bubble_point), there's no indication of when this brine-specific calculation is appropriate versus other fluid types or methods.

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