rta_blasingame

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

No annotations are provided, so the description carries full burden. It indicates a read-only computation ('Compute', 'Calculates') but does not disclose any side effects, assumptions, or validation behavior. For a calculation tool, this is adequate but lacks explicit transparency.

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: a one-sentence purpose followed by an Args block. Every sentence adds value, and the structure is front-loaded with the main computation goal.

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?

The description lists all computed quantities, matching the likely output schema. It covers inputs, outputs, and context for type curve matching. However, it does not mention the output schema existence or return structure, which is documented separately.

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% (only titles in properties), but the description adds units and context: 'Time values (days or months)', 'Bottomhole flowing pressures (psi)', 'Initial reservoir pressure (psi)'. This adds value beyond the bare schema, though constraints or relationships are not explained.

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 it computes Blasingame rate-normalized integral and derivative for type curve matching, listing the specific outputs: material balance time, normalized rate, rate-integral, rate-integral-derivative. This distinguishes it from similar RTA tools like rta_agarwal_gardner or rta_normalized_rate.

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 mentions 'for type curve matching' but does not explicitly state when to use this tool versus alternatives like rta_agarwal_gardner or rta_material_balance_time. No exclusion criteria or contextual guidance is provided.

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