calculate_breakeven_price

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

With no annotations, the description reveals the bisection algorithm and that it finds the price where discounted net cash flow equals zero. However, it does not disclose convergence behavior, error handling, or what happens if no solution exists.

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: one sentence for the main purpose, one sentence for the method, and a bulleted list of arguments. Every sentence earns its place, though the method detail could be merged.

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 (present but not shown), the description covers the tool's purpose, parameters, and underlying algorithm. It is adequate for an agent to use the tool correctly, though it omits edge cases and assumptions.

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?

Schema description coverage is 0%, but the description provides brief explanations for each parameter (e.g., monthly_production_bbl as 'Monthly oil production (bbl) per period') and notes defaults. This adds meaningful context beyond the schema's empty 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 calculates the breakeven oil price, defined as the minimum price for NPV=0. This is a specific verb+resource combination that distinguishes it from sibling tools like calculate_npv or calculate_price_sensitivity.

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 implies usage when a breakeven price is needed, but does not provide explicit when-to-use, when-not-to-use, or alternative tools. No guidance on exclusions or prerequisites.

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