calculate_indonesian_sw

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

No annotations are provided, and the description fails to mention any behavioral traits such as side effects, rate limits, or error handling. It only describes the calculation, missing the opportunity to disclose important operational details.

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 well-structured with a clear intro and parameter list, but it is slightly verbose. Every sentence is relevant, though it could be more concise.

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?

The description covers all 8 parameters, including defaults, and references the formula. With an output schema present (context shows true), the return values are likely documented elsewhere, making this 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?

The description includes a detailed parameter list with explanations and default values, which significantly adds meaning beyond the input schema's minimal title and type. This is especially valuable given the schema's 0% 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 calculates water saturation using the Indonesian equation (Poupon and Leveaux, 1971) and specifies it's for high-Vshale formations, distinguishing it from siblings like calculate_archie_sw and 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 provides context for when to use this tool (very shaly sands) by stating it's better than Archie/Simandoux, but it does not explicitly list exclusions or alternatives.

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