calculate_bit_pressure_drop

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

With no annotations, the description is the sole source of behavioral info. It correctly identifies the tool as a calculation with no side effects, but does not explicitly state that it is a pure function or describe error handling for invalid inputs.

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 includes the formula upfront. The parameter list is clear, but the inclusion of the formula could be considered slightly redundant given the parameter descriptions. Overall, it efficiently conveys the necessary information.

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 defined structurally. However, the description does not mention the output units or typical result interpretation, which would be helpful for an agent. The lack of usage guidelines also reduces completeness.

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?

Each parameter is given a brief definition with units (gpm, ppg, in^2), which adds meaning beyond the schema titles. However, the descriptions are minimal and do not elaborate on typical ranges or validation.

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?

Description clearly states the tool calculates pressure drop across the bit using the provided formula. It specifies the exact resource (bit pressure drop) and includes the mathematical relationship, leaving no ambiguity about its function.

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. The description does not mention applicable scenarios, prerequisites, or situations where a different tool would be appropriate.

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