calculate_dogleg_severity

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

The description explains the output format (deg/100ft or deg/30m) and parameter meanings, but does not disclose any behavioral traits like read-only nature, error behavior, or assumptions. Since no annotations are provided, the description could be more transparent.

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 and well-structured: a one-line purpose, output specification, and a clear argument list. Every sentence is necessary and efficient.

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 parameter semantics and output format, but lacks context about when to use this tool, any prerequisites (e.g., needing two survey stations), or how it fits within the larger workflow. An output schema exists, so return value details are not required.

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 compensates fully by listing each parameter with its meaning and units (e.g., 'md1: Measured depth at station 1'). This adds significant value.

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's purpose: calculating dogleg severity between two survey stations, with output units specified. It distinguishes itself from the many sibling 'calculate_*' tools by being specific, but does not explicitly differentiate from similar survey tools.

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 (e.g., other calculation tools). There is no mention of prerequisites, typical use cases, or when not to use it.

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