calculate_permeability_coates

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

The description provides the equation and parameter constraints (fraction v/v) but does not disclose assumptions, default permeability units, or limitations. No annotations are present to supplement behavioral traits.

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 highly concise, front-loading the purpose and equation, then listing parameters in a structured Args block. No superfluous information is present.

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?

While the description includes the equation and parameter definitions, it omits the units of the output (presumably md) and any underlying assumptions (e.g., water-saturated formations). An output schema exists but is not leveraged in the description.

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 Args section in the description adds significant meaning to all four parameters (phi, bvi, ffi, c) beyond the schema which only has titles. It clarifies units, ranges, and defaults, with 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 'Estimate permeability using Coates (1991) equation', providing a specific verb and resource. It distinguishes from sibling tools like calculate_permeability_timur by naming the specific equation.

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 guidance is given on when to use this tool over alternatives like calculate_permeability_timur or other permeability estimators. The description lacks any contextual comparison or usage scenarios.

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