pz_analysis

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

The description explains that the tool fits a linear trend and estimates OGIP, and optionally computes recoverable gas. However, it does not disclose whether the tool modifies data, its assumptions (e.g., linearity), or any prerequisites. With no annotations, the description carries the full burden.

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 mostly concise and front-loaded with the core purpose. The 'Args' section repeats some parameter names but adds value. The phrase 'The #1 reservoir engineering spreadsheet calculation' is somewhat unnecessary but does not severely detract.

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 an output schema is present, the description does not need to detail return values. However, it lacks discussion of assumptions (e.g., linearity), data quality requirements, or common pitfalls. It adequately covers inputs but is not fully complete for a complex analysis 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 input schema has no descriptions (0% coverage), but the tool description adds detailed semantics for each parameter: pressures are reservoir pressures or P/Z in psi, cumulative gas is in Bcf, and abandonment pressure is optional in psi for recoverable gas. 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 tool performs a P/Z vs cumulative gas production analysis to estimate Original Gas In Place (OGIP). The verb 'Fits' and resource 'OGIP' make the purpose specific, but it does not explicitly differentiate from sibling tools like 'volumetric_ogip' or 'rta_flowing_material_balance'.

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 guidance is provided on when to use this tool versus alternatives. The claim 'The #1 reservoir engineering spreadsheet calculation' is subjective and does not help an agent decide between similar tools.

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