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

The description provides no details beyond the conversion itself. With no annotations, it should disclose any rounding behavior, precision, or error handling. This is a gap for a simple but precise operation.

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?

Single sentence, no fluff, perfectly concise for the tool's simplicity.

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, single parameter, and existence of output schema, the description is nearly complete. It could mention the output unit (hectares) explicitly, but it's inferred from the tool name.

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 provides 'Area in acres' for the parameter, which is already clear. Description adds no further semantic value, meeting the baseline for 100% schema coverage.

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 clearly states 'Convert acres to hectares', using a specific verb and resource. It distinguishes from sibling tools like 'celsius_to_fahrenheit' by naming the exact conversion.

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?

No explicit guidance on when to use this tool versus alternatives. Since it's a straightforward unit conversion, usage is implied, but among many conversion siblings, some context would help.

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