area_converter

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

No annotations are provided, so the description alone must carry the behavioral burden. It states the conversion action and unit set, but does not disclose return format, handling of invalid units, precision/rounding, or case-sensitivity of unit strings. It is minimally informative but not misleading.

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 two short sentences with no filler. It front-loads the core purpose and unit set, then lists the required inputs. Every part earns its place.

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 simple conversion tool with no output schema, the description covers the essential inputs and unit domain. It is missing a clear statement of the output representation and any constraints around unit strings, which would help an agent invoke it correctly in ambiguous cases.

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 schema has 0% coverage and no enums, so the description must compensate. It does list the relevant units and names all three parameters, giving agents the allowed unit vocabulary. However, it does not explicitly map value/from/to to their roles or clarify accepted input formats beyond that list.

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 a specific verb and resource: 'Convert area,' and enumerates the exact unit pairs (mm²/cm²/m²/km² ↔ in²/ft²/yd²/acre/ha). This clearly distinguishes it from sibling converters like length_converter or temperature_converter.

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 implies usage by naming area unitscars, but it does not explicitly say 'use this for area conversions' or contrast it with alternatives. The sibling list makes the distinction inferable, yet there is no direct when-to-use or when-not-to-use guidance.

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