area_conversion

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the conversion function without detailing traits like supported units, precision, error handling, or output format. This is inadequate for a tool with parameters and no output schema, leaving critical behavioral aspects unspecified.

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 a single, efficient sentence in Chinese that directly states the tool's function without unnecessary words. It is appropriately sized for a simple conversion tool, though it could be more informative. The structure is front-loaded with the core purpose, but lacks elaboration that might be needed for clarity.

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 complexity (3 parameters, no annotations, no output schema), the description is incomplete. It does not explain the return values, error conditions, or behavioral details necessary for effective use. While the purpose is stated, the lack of annotations and output schema means the description should provide more context to be fully helpful.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'different area units' which hints at 'from_unit' and 'to_unit', but does not specify allowed units or formats. It implies 'value' as the numeric input but adds no semantic context beyond the schema. This partially addresses parameters but falls short of fully compensating for the coverage gap.

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 the tool's purpose as converting between area units, which is clear but vague. It specifies 'different area units' without naming examples or distinguishing from sibling tools like length_conversion or volume_conversion, though the tool name itself provides some differentiation. It avoids tautology by not merely restating the name/title.

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. It does not mention sibling tools like length_conversion or volume_conversion, nor does it specify prerequisites or exclusions. Usage is implied by the general purpose but lacks explicit context for selection.

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