calculate_wellbore_tortuosity

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, safety (read-only nature), or error handling. It fails to inform the agent that this is a pure computation with no external side effects.

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 purpose statement and an efficient Args list. However, it could be more structured by front-loading the purpose more prominently. It wastes no sentences but the Args section somewhat duplicates schema fields.

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 tool has an output schema, so return values are covered. The description explains tortuosity's impact, but lacks context on data constraints, error conditions, or any prerequisite understanding. It is adequate but not comprehensive for a calculation tool without annotations.

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 (only titles), but the description's Args section fully explains each parameter: md as list of measured depths, inclination/azimuth in degrees, and unit with allowed values and default. This adds complete semantic meaning 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, with a concise explanation of what tortuosity measures. However, it does not explicitly distinguish itself from sibling tools like calculate_dogleg_severity, which could cause confusion for an AI agent.

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 no guidance on when to use this tool versus alternatives. It does not mention conditions for use, prerequisites, or scenarios where other tools might be more appropriate, leaving the agent without decision support.

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