calculate_permeability_timur

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

With no annotations, the description provides the equation and parameter units but omits behavioral details like output format, assumptions, or limits of the model.

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 extremely concise: one line for the equation, one line each for parameters. Every sentence adds value with no 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?

For a simple two-parameter equation, the description is fairly complete given an output schema exists. It lacks usage guidance but covers the core logic and parameter constraints.

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 schema only provides type and title; the description adds meaning by defining phi as porosity (0-1 fraction) and swirr as irreducible water saturation (0-1 fraction), compensating for 0% schema 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 estimates permeability using the Timur equation, explicitly providing the formula. It distinguishes from siblings like calculate_permeability_coates by specifying the model.

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 Timur versus other permeability models (e.g., Coates). The description lacks context about applicability conditions.

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