Drip Rate Calculator

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does indicate a side-effect-free calculation and the two outputs, but it does not describe the formula relationship, units of the returned rates, or how the optional drop_factor default is applied.

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?

A single 10-word sentence with no filler, front-loading the core action and outputs. Every word earns its place for a simple calculator tool.

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?

For a three-parameter calculator with 100% schema coverage and an output schema, the description plus schema is largely sufficient to invoke the tool correctly. It loses a point only because the lack of usage guidance and behavioral annotations leaves selection and safety to inference.

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?

Schema description coverage is 100%, so the input schema already documents all parameters with units, defaults, and constraints. The description adds only a mild conceptual link between volume_ml/time_hours and the volume/time rate, and between drop_factor and the gravity drip rate, which is not enough to raise it above the high-coverage baseline.

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 uses a specific verb ('Calculate') and names the exact resources computed: a volume/time rate and a gravity drip rate. This clearly identifies the tool as an IV infusion calculator and distinguishes it from the sibling Parkland formula and BSA calculators.

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 given about when to choose this tool over the available alternatives, and no exclusions or prerequisites are stated. The agent must infer from the tool name alone that it applies to drip-rate calculations rather than Parkland resuscitation or BSA.

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