calculate_wellbore_tortuosity

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

No annotations are provided, so the description must convey behavioral traits. It only explains the metric and inputs, not side effects, prerequisites, or output behavior. The description is minimal in this regard.

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, with a clear front-loaded purpose statement followed by a brief explanation and parameter details. Every sentence adds value without 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?

The description explains the function and inputs, but given that an output schema exists, it does not need to detail outputs. However, it lacks edge cases (e.g., array length mismatches) and validation behavior, making it adequate but not comprehensive.

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 input schema has 0% description coverage, but the description's 'Args' section provides meaningful explanations for each parameter (e.g., 'List of measured depths', 'inclination (degrees)', 'unit: feet or meters'). This adds value beyond the 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 the tool calculates 'wellbore tortuosity index from survey data' and explains what tortuosity measures. The verb 'calculate' and resource are specific, distinguishing it from other calculation tools in the sibling list.

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 about inputs (survey data) but lacks explicit guidance on when to use this tool versus alternatives, such as when not to use it or specific conditions. The purpose is implied but not fully explicit.

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