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 describes the analytical method and output (determining sqrt(k)*xf), but lacks critical behavioral details: it doesn't specify if this is a read-only calculation or has side effects, what units or format the output takes (though an output schema exists), error handling, or assumptions like data alignment. For a computational tool with no annotation coverage, this leaves significant gaps in understanding its operation.

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 well-structured and appropriately sized: it starts with the analytical purpose, explains the mathematical basis, and lists parameters with units. Every sentence adds value, with no redundant information. It could be slightly more front-loaded by emphasizing the tool name's action earlier, but overall it's efficient and clear.

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 tool's complexity (reservoir engineering analysis), the description provides a solid foundation: it explains the method, parameters with semantics, and intended output. With an output schema present, it doesn't need to detail return values. However, it lacks information on behavioral aspects like computational limits or validation, which would enhance completeness for a tool with no annotations.

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?

Schema description coverage is 0%, so the description must compensate fully. It successfully adds meaning beyond the schema by explaining each parameter's purpose and units: 'rates: Production rates (bbl/d or Mcf/d)', 'times: Time values (days)', 'flowing_pressures: Bottomhole flowing pressures (psi)', and 'initial_pressure: Initial reservoir pressure (psi)'. This clarifies the physical significance and expected data, which the schema titles alone do not provide.

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 performs 'Square root of time analysis for linear flow identification' and explains the mathematical relationship (Pi-Pwf)/q vs sqrt(t) yields a straight line during fracture-dominated linear flow. It specifies the purpose is to determine sqrt(k)*xf from the slope, which is specific to reservoir engineering analysis. However, it doesn't explicitly differentiate from sibling RTA tools like rta_agarwal_gardner or rta_blasingame, though the mathematical approach is distinct.

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 by stating 'During fracture-dominated linear flow,' suggesting this tool is specifically for that flow regime. However, it doesn't provide explicit guidance on when to choose this over alternative RTA methods (like rta_material_balance_time or rta_normalized_rate) or mention prerequisites such as data quality requirements. The context is clear but lacks comparative or exclusionary advice.

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