convert_area

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

No annotations are provided, but the description mentions 'Returns: {input}' which is ambiguous and possibly misleading (expected: converted value). It does not detail behavioral aspects like rounding, precision, or error handling. However, given the tool's simplicity and schema validation (enums), the lack of detail is not critical.

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?

Description is two concise sentences plus a reference. No unnecessary words, and information is front-loaded. Every sentence serves a purpose.

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 (conversion of area units), the description covers the essential: purpose, units, typical use cases, and a pointer to related tools. The schema handles parameter details. The return value is vaguely described, but an output schema is not provided. Overall, it's adequate for the context.

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 100%, so the schema already documents all parameters. The description repeats parameter names (value, from, to) but adds no new insight. The note 'Returns: {input}' is vague and does not clarify output format, which could reduce utility.

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?

Description clearly states 'Convert area' and lists specific units (m², km², ha, etc.). It identifies use cases (real estate, agriculture, construction). However, it does not explicitly distinguish itself from sibling conversion tools (e.g., convert_distance) beyond the unit list, which is 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?

Description suggests use cases (real estate, agriculture, construction) and references list_bundles for related calculators. However, it lacks explicit guidance on when not to use this tool or how it compares to alternatives. The reference to list_bundles is vague.

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