Redesign Airfoil

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

With no annotations, the description carries the full burden. It does disclose one real side effect: with save_as the new geometry is written into the library under that name and as a .dat file next to it. However, it never states what happens to the original airfoil when save_as is omitted, whether changes are reversible, or what the backup flag actually protects.

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?

Front-loads the concrete action and its mechanism before the conditional save behavior, in three short sentences. The parenthetical about Profili's internal recipe is flavor rather than instruction, but it is brief enough not to obstruct scanning.

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?

This is a mutating geometry tool with no annotations, 8 parameters, and 0% schema coverage; the description explains only a fraction of them. An output schema exists so return values need not be described, but the gaps around in-place modification, the backup flag, and the two camber/thickness location parameters leave real ambiguity.

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 thickness and camber as chord fractions and explains save_as, but leaves backup, x_camber, x_thickness, install_dir, and name entirely undocumented, and gives no units or ranges for the rescale values.

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?

Names a specific verb and effect: rescale max thickness and/or camber as chord fractions via XFOIL GDES TSET, and adds the save_as side effect. An agent can tell this mutates geometry rather than reading it (get_airfoil_geometry) or analyzing it, though no sibling is named explicitly.

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?

Usage is implied by the purpose ('the same modify airfoil recipe Profili uses internally') but there is no explicit when-to-use, when-not-to-use, or comparison to alternatives such as import_airfoil_dat or export_airfoil_dat. The agent must infer that this is the right tool for reshaping rather than loading or analyzing.

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