calculate_archie_sw

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

No annotations are provided, so the description carries full burden. It explains the formula and parameters but does not disclose behavior for edge cases (e.g., zero or negative inputs) or error handling. This leaves gaps in behavioral understanding.

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 front-loaded with purpose, followed by the formula and parameter list. It is clear and structured, though the formula is slightly verbose and may not be necessary for agent understanding.

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 that an output schema exists, the description adequately covers purpose, parameters, and formula. It could mention units for all parameters or edge cases, but overall it is fairly complete for a calculation tool.

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?

With 0% schema description coverage, the description fully compensates by providing meaning, units, and defaults for each parameter (e.g., 'rt: True formation resistivity (ohm-m)'). This adds significant value beyond the bare schema.

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 'Calculate water saturation using Archie equation (clean sands).' This specifies the exact resource and operation, and distinguishes from sibling tools for shaly sands like calculate_simandoux_sw.

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 implies usage for clean sands but does not explicitly state when to use this versus alternatives like calculate_simandoux_sw. It lacks explicit when-to, when-not-to, or prerequisite guidance.

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