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 mentions the models used (Vogel IPR and simplified vertical lift) but doesn't describe what the tool returns (though an output schema exists), computational characteristics, assumptions, or limitations. For a complex engineering calculation with 6 parameters, this leaves significant behavioral gaps unexplained.

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 begins with the purpose, mentions the models used, then lists parameters with clear explanations. Every sentence earns its place, though the parameter explanations could be slightly more concise. No redundant information is present.

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 (6 parameters, engineering calculation) and the presence of an output schema (which handles return values), the description is moderately complete. It excels at parameter explanations but lacks behavioral context about assumptions, limitations, or when to use. With no annotations, it should provide more operational guidance for a tool of this nature.

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?

The description provides excellent parameter semantics beyond the schema. The schema has 0% description coverage (only titles), but the description clearly explains each parameter's meaning, units, and defaults where applicable (e.g., 'Average reservoir pressure in psi,' 'Productivity index in bbl/day/psi,' 'default 8000'). This fully compensates for the schema's lack of descriptions.

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 purpose: 'Simplified nodal analysis: find IPR/VLP intersection for operating point.' It identifies the exact technical method (Vogel IPR and simplified vertical lift model) and distinguishes this from sibling tools like 'calculate_annular_velocity' or 'calculate_hydrostatic_pressure' which serve different petroleum engineering functions.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While the description mentions it's for 'simplified nodal analysis,' it doesn't specify scenarios where this simplified approach is appropriate versus more complex alternatives, nor does it mention prerequisites or limitations. The sibling tools list includes many calculation tools, but no comparison is offered.

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