rta_material_balance_time

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

No annotations are present, so the description carries full burden. It discloses the mathematical operation and its purpose, but does not mention output structure, units, array length constraints, or error handling. The behavioral disclosure is adequate but minimal.

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 two short paragraphs plus a docstring-style args listing. It is mostly concise, though the args list could be integrated more smoothly. Overall, it is effective without significant redundancy.

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?

An output schema exists, so return values are handled. The tool has only two required parameters. The description explains the formula and transform purpose, but given the rich set of sibling tools, additional context on when this transform is appropriate would improve completeness.

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%, so the description must compensate. It mentions the parameter names 'cumulative_production' and 'rate' but adds no additional constraints, units, or format guidance beyond the bare names. This provides marginal value over 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?

The description clearly states the tool computes material balance time via the formula tMB = Np / q and explains it is a Blasingame x-axis transform for decline type curve matching. This is specific and distinguishes from sibling tools like rta_blasingame or rta_agarwal_gardner.

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 provides no guidance on when to use this tool versus alternatives such as rta_blasingame or rta_normalized_rate. Given the large number of sibling RTA tools, explicit context on prerequisites or comparative use cases is lacking.

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