petropt/petro-mcp

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

No annotations are provided, so the description carries the full burden. It mentions the tool's purpose and usage but lacks behavioral details such as computational requirements, error handling, output format, or any side effects. The description does not contradict annotations, but it fails to provide sufficient behavioral context for a tool with no annotation coverage.

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 appropriately sized and front-loaded with the core purpose in the first sentence, followed by usage context and detailed parameter explanations. It is efficient with no wasted sentences, though the parameter section could be slightly more integrated into the flow.

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 the complexity of a computational tool with 4 parameters, no annotations, and an output schema (which handles return values), the description is mostly complete. It covers purpose, usage, and parameter semantics adequately, but lacks behavioral transparency details like error conditions or performance expectations.

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 explaining all four parameters: 'times' as time values in days or months, 'rates' as production rates, 'flowing_pressures' as bottomhole flowing pressures in psi, and 'initial_pressure' as initial reservoir pressure in psi. This adds essential meaning beyond the bare schema.

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 ('Compute Normalized Pressure Integral'), the resource ('for flowing material balance'), and distinguishes it from siblings by specifying its unique purpose of smoothing noisy production data for flow regime identification and FMB analysis, unlike other RTA tools like rta_blasingame or rta_flowing_material_balance.

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 ('Used for flow regime identification and FMB analysis') but does not explicitly state when to use this tool versus alternatives like rta_normalized_rate or rta_material_balance_time, nor does it provide exclusions or prerequisites for its application.

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