recovery_factor

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

Describes a straightforward mathematical calculation with no side effects or destructive actions. While no annotations are provided, the description accurately reflects the tool's behavior and does not hide any surprises.

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: formula in first line, followed by explanation of usage and clear parameter descriptions. No extraneous text.

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 tool's simplicity and the presence of an output schema, the description covers all necessary information: formula, parameter meaning, unit consistency, and applicability to both oil and gas.

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?

Adds significant meaning beyond the schema by explaining each parameter (original in place and cumulative production) and emphasizing unit consistency. The schema had 0% coverage, and the description fully compensates.

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?

Clearly states it calculates recovery factor (RF = Np/N or Gp/G) and specifies it works for both oil and gas. This distinguishes it from sibling tools like calculate_eur or decline 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?

Implied usage for simple RF calculation, but lacks explicit guidance on when to use vs alternatives such as EUR calculations or decline curve analysis. No exclusion or alternative tools mentioned.

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