rta_permeability

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

No annotations provided; the description explains the calculation outcome (permeability or sqrt(k)*xf) but does not disclose any behavioral traits like read-only nature, side effects, or output format.

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 structured with a purpose sentence followed by parameter definitions, but is slightly verbose with the 'Args' section; still clear and 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?

Given the tool's complexity (6 params, calculation logic), the description covers the main purpose and parameter roles. Output schema exists but is not referenced; overall adequate.

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 provides detailed explanations for each parameter (slope, net pay, porosity, etc.) and explains the mathematical logic, fully compensating for the 0% schema description coverage.

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 extracts permeability from RTA linear flow analysis using the slope from sqrt(t) analysis, distinguishing it from other RTA siblings like rta_agarwal_gardner or rta_blasingame.

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 when to use it (when fracture half-length is known vs. not) but does not explicitly compare to alternative tools or mention prerequisites beyond parameter units.

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