calculate_price_sensitivity

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

No annotations provided. Description describes inputs and function but does not disclose whether the tool has side effects, authorization requirements, or edge cases. It is a pure calculation, but that is implied rather than stated.

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?

Description is front-loaded with the core purpose and uses a clear Args format. Every sentence is necessary given the lack of schema descriptions. Could potentially be more concise but is well-structured.

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?

Covers inputs comprehensively but does not describe output format despite the output schema existing. While the schema may specify types, the description could alert the agent to the return structure (e.g., list of NPV values). Adequate but not complete.

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 coverage is 0%, so description compensates by explaining each parameter in the Args block (e.g., 'monthly_oil_bbl: Monthly oil production (bbl) per period.'). This adds meaning beyond the schema's field names and types.

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?

Description clearly states 'Calculate NPV across multiple price scenarios for sensitivity/tornado charts.' This is a specific verb-resource pair and distinguishes from sibling tools like calculate_npv or calculate_breakeven_price.

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 use for sensitivity analysis via 'for sensitivity/tornado charts', but no explicit when-to-use, when-not-to-use, or alternatives. Among many economic tools, clearer guidance would help.

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