rta_npi

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

No annotations are provided, so the description must disclose behavioral traits. It explains that NPI integrates pressure-normalized rate to smooth noisy data. It does not mention destructive actions, auth needs, or rate limits. The description is adequate but not comprehensive.

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 with two paragraphs and around five sentences. It front-loads the main purpose and parameter list. No wasted words, though it could be slightly more streamlined.

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 tool has an output schema, so return values are likely defined elsewhere. However, the description lacks preconditions like array length consistency or error handling. For a numerical tool with four required inputs, more completeness about expected input formats would be beneficial.

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%, but the description adds units and meaning for each parameter (e.g., times in days/months, flowing_pressures in psi). This compensates for the schema gap, though it could provide more constraints like array length matching.

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 the Normalized Pressure Integral for flowing material balance, and specifies its use for flow regime identification and FMB analysis. This distinguishes it from similar RTA siblings.

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 indicates usage for flow regime identification and FMB analysis, providing context. However, it does not explicitly state when to avoid this tool or mention alternatives among the many sibling RTA tools.

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