rta_material_balance_time

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

No annotations are provided, so the description carries the burden. It explains the mathematical operation but does not disclose potential edge cases (e.g., division by zero if rate is zero) or array size requirements. The behavioral context is moderate but incomplete.

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 very concise: a formula, a one-sentence purpose, and brief parameter descriptions. No unnecessary words, and key information is front-loaded.

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?

With an output schema available, return values need not be detailed. However, the description lacks context on workflow integration (e.g., that this is typically a preliminary step in RTA), and does not mention constraints like matching array lengths. It is adequate but could be more comprehensive.

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 description adds meaning beyond the input schema by naming 'cumulative_production values' and 'instantaneous production rates', whereas the schema only provides titles and types. This is helpful, though more detail on units or constraints would improve it.

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 what the tool does: compute material balance time via the formula tMB = Np/q. It explicitly mentions its role as the Blasingame x-axis transform for decline type curve matching, distinguishing it from other similar tools in the sibling list.

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 explicit guidance on when to use this tool versus alternatives like rta_blasingame or rta_normalized_rate. The context of Blasingame analysis is implied but not elaborated, and there is no mention of prerequisites or exclusions.

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