Analyze Naca

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context that the schema cannot convey: XFOIL generates the geometry internally and the library is not modified, which tells the agent this call is self-contained and non-persistent. It says nothing about runtime cost, whether the resulting polar is stored, or how invalid NACA codes are handled.

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 front-loaded sentence that states the action, the input domain, and the mechanism with zero filler. Nothing is repeated and nothing is padding.

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?

An output schema exists, so return values need not be described, but the tool is an 8-parameter computational call with no annotations and no parameter documentation. For that complexity the description is too thin — an agent cannot set Reynolds number, Mach, or the alpha sweep without guessing.

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 0% across 8 parameters, so the description must compensate and largely does not. It clarifies the naca_code format (4/5-digit), but the remaining seven inputs — re, mach, ncrit, alfa_start, alfa_end, alfa_step, install_dir — receive no explanation of units, ranges, or effect on the solve.

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 names a specific verb and output ('Compute a polar') and a specific input domain ('any NACA 4/5-digit airfoil'), which is concrete enough to distinguish this from generic polar tools. It does not name the sibling analyze_airfoil or state how this differs from it beyond the NACA-code constraint, so sibling differentiation is only implicit.

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 phrase 'without touching the library' implies the selection condition: use this when you have a NACA designation and do not want to import or locate an airfoil first. However, no alternative tool is named and there is no explicit when-not-to-use guidance, so the agent must infer the routing decision.

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