calculate_operating_netback

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

Discloses the full formula and conversion factor. With no annotations, the description carries the burden. It covers calculation steps but does not address error handling or assumptions beyond defaults.

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?

Extremely concise: one-line purpose, formula, conversion, then compact Args list. No extraneous sentences.

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 output schema exists (not shown but present), the description needs only to explain inputs and calculation, which it does thoroughly. Complete for a calculator 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?

Each parameter is described with units and defaults (e.g., 'Oil price ($/bbl)'). Schema description coverage is 0%, so the description fully compensates by adding meaning beyond the schema.

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?

Clear statement of tool function: 'Calculate operating netback per BOE.' Formula and conversion (Gas at 6 Mcf/BOE) are provided. Distinct from sibling tools focusing on other metrics.

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?

Implies usage for computing netback from provided inputs, but does not explicitly differentiate from related economic tools like calculate_breakeven_price or calculate_well_economics. No when-not-to-use guidance.

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