calculate_nozzle_tfa

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

The description fully discloses the calculation formula and input units, making the behavior transparent. Since no annotations are provided, the description carries the burden and does so adequately, though it does not mention that the tool is pure and side-effect-free.

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 (three sentences) and front-loaded with the purpose, including the formula in a clear format. No extraneous text.

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?

Given the tool's simplicity, the description adequately covers input and the calculation. An output schema exists, so return values need not be explained. The description is complete for the tool's purpose.

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 description explicitly defines the single parameter 'nozzle_sizes' as a list of integers in 32nds of an inch with an example, adding significant meaning beyond the schema's minimal type definition. With 0% schema coverage, this is essential and well-handled.

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 total flow area (TFA) of bit nozzles, using a specific verb and resource. It is distinct from sibling calculation tools like calculate_annular_velocity or calculate_ecd.

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, nor does it mention any prerequisites or exclusions. The tool's purpose is self-evident, but explicit usage context is missing.

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