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. While it clearly states this is a calculation tool, it doesn't mention important behavioral aspects like whether this is a pure computation (no side effects), what units the output is in, error handling for invalid inputs, or performance characteristics. The formula suggests it's deterministic, but this isn't explicitly stated.

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 structured and concise: it starts with the purpose and formula, then lists each parameter with clear explanations. Every sentence earns its place, with no redundant information. The two-part structure (purpose/formula then parameters) makes it easy to parse.

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 there's an output schema (which handles return values), the description provides excellent coverage of the calculation purpose and parameter semantics. However, for a tool with no annotations, it could benefit from explicitly stating this is a pure computation with no side effects. The presence of an output schema reduces the need to describe return values, making this 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 information for all three parameters: flow_rate_gpm is 'Flow rate in gallons per minute', mud_weight_ppg is 'Mud weight (ppg)', and tfa_sqin is 'Total flow area of nozzles (in^2)'. This adds essential meaning beyond the schema's basic type information.

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 explicitly states the specific calculation being performed ('Calculate pressure drop across the bit') and provides the exact formula (dP = MW * Q^2 / (12032 * TFA^2)). This clearly distinguishes it from sibling tools like calculate_annular_velocity or calculate_hydrostatic_pressure which perform different 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. While the formula itself implies it's for drilling engineering calculations, there's no explicit context about when this specific calculation is needed or what problems it solves compared to other pressure-related tools in the sibling list.

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