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 what the tool returns (F vs Et plot data for diagnostics) but doesn't describe computational behavior, error handling, performance characteristics, or whether this is a read-only calculation versus something that modifies data. For a complex 14-parameter tool with no annotation coverage, this is insufficient.

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 with a clear purpose statement followed by detailed parameter documentation. While comprehensive, every sentence serves a purpose - the first paragraph explains what the tool does, and the Args section provides essential parameter context. It could be slightly more concise in the parameter explanations but remains efficient.

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 (14 parameters, no annotations, but with output schema), the description is moderately complete. It thoroughly documents parameters and states the return purpose, but lacks behavioral context, usage guidelines, and error handling information. The presence of an output schema reduces the need to describe return values, but more operational context would be helpful for this sophisticated engineering tool.

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 comprehensive parameter documentation with units and explanations for all 14 parameters, despite 0% schema description coverage. Each parameter is clearly explained with its physical meaning and measurement units, adding significant value beyond the bare schema. The only minor gap is that it doesn't explicitly state array length requirements or consistency between arrays.

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: performing oil material balance analysis using the Havlena-Odeh method to identify drive mechanisms and estimate OOIP. It distinguishes itself from sibling tools by focusing on this specific reservoir engineering technique rather than general calculations or other analysis methods.

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 it mentions what the tool does, it doesn't indicate when this method is appropriate, what prerequisites are needed, or how it compares to other material balance or reservoir analysis 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.