calculate_annular_velocity

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

The description includes the formula and parameter descriptions but does not explain output format or units. Since no annotations are provided, the description's minimal disclosure is adequate for a straightforward calculation but could be improved.

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: a single-line formula followed by clear parameter definitions. It is efficient, though slightly informal with the docstring style.

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 the essential formula and parameter definitions but omits the output unit (assumed ft/min) and any usage constraints. For a simple calculation tool, it is sufficient 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?

With 0% schema description coverage, the description compensates by explaining each parameter's meaning and units (e.g., 'Flow rate in gallons per minute'). This adds significant value beyond the bare 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 states 'Calculate annular velocity' and provides the explicit formula, clearly defining the tool's function. Among many 'calculate_*' siblings, this tool is uniquely identified by its formula and required parameters.

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 siblings or alternatives. The description lacks any context about prerequisites, suitable scenarios, or limitations.

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