calculate_simandoux_sw

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

With no annotations, the description carries the full burden of behavioral disclosure. It only lists parameters and defaults, omitting return format, output unit, error handling, or constraints like phi must be between 0 and 1.

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: one sentence for purpose followed by a structured Args list. No redundant information. Could be slightly more compact, but it is well-organized and front-loaded with the main purpose.

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 presence of an output schema, the description doesn't need to explain return values. It covers equation name, inputs with units and defaults, but lacks explicit input constraints (e.g., phi and vshale should be 0-1) and does not provide the equation or typical ranges.

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%, so the description must compensate. It provides units and ranges for some parameters (e.g., 'ohm-m', 'fraction v/v, 0-1') and defaults for a, m, n. This adds meaningful context beyond the schema, though not all parameters have ranges.

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 calculates water saturation using the Simandoux equation for shaly sands, which is a specific verb+resource combination. This distinguishes it from siblings like calculate_archie_sw (clean sands) and calculate_indonesian_sw (another shaly sand 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 provided on when to use this tool versus alternatives such as calculate_archie_sw or calculate_indonesian_sw. There is no mention of prerequisites, data requirements, or conditions under which this equation is appropriate.

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