petropt/petro-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an 'estimate' tool, which implies approximation rather than exact calculation, but doesn't disclose accuracy limitations, computational characteristics, or what the output represents. More behavioral context would be helpful for a calculation tool.

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 perfectly front-loaded with the core purpose in the first sentence, followed by parameter explanations. Every sentence earns its place, with no wasted words or redundant 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?

Given this is a calculation tool with 2 parameters, no annotations, but with an output schema (which handles return values), the description provides adequate context. It covers the purpose, method, and parameter semantics reasonably well, though more behavioral transparency would improve completeness.

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 well by explaining both parameters: 'pressure_psi' gets units (psi) and 'gas_sg' gets definition (air = 1.0) and valid range (0.55-1.0). This adds significant meaning beyond the bare schema, though it doesn't cover all possible semantic nuances.

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 specific action ('Estimate hydrate formation temperature') and the method used ('gas-gravity method (Katz chart)'). It distinguishes this tool from sibling tools like 'calculate_hydrate_inhibitor' by focusing on temperature estimation rather than inhibitor 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 implies usage context through the method name ('gas-gravity method') and parameter ranges, but doesn't explicitly state when to use this tool versus alternatives. No explicit guidance on when-not-to-use or named alternatives is provided.

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