pz_analysis

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

The description explains the method (linear fit) and that OGIP is estimated, but does not disclose assumptions (e.g., linear P/Z relationship for volumetric gas reservoirs), limitations, or what happens with poor data. It also does not describe the return value beyond estimation. Since no annotations exist, the description carries full burden, but it provides moderate transparency.

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 concise with two short paragraphs. The first sentence states the purpose, the second adds method detail, and the third provides parameter explanations in a clean args list. Every sentence is necessary and informative with no waste.

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 and the existence of an output schema, the input description is nearly complete. It would benefit from a brief note on what the output contains (e.g., OGIP value, fit statistics), but since output schema is present, this is partially covered. Omitting prerequisites or data quality notes is a minor gap.

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 explains all three parameters: pressures as psi or P/Z, cumulative_gas in Bcf, and abandonment_pressure as optional for recoverable gas. This adds units and context beyond the schema. However, it does not mention array length matching or validation, so not perfect.

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 that the tool performs gas material balance analysis using P/Z vs cumulative gas production to estimate Original Gas In Place (OGIP). This is a specific verb+resource combination that distinguishes it from sibling tools like 'volumetric_ogip' (volumetric estimation) and 'rta_material_balance_time' (rate transient analysis).

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 other OGIP estimation methods (e.g., volumetric, RTA). No mention of prerequisites (e.g., reservoir must be volumetric) or when not to use it (e.g., if data is noisy or non-linear). The description lacks contextual usage advice.

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