ag_calc_unit_convert

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

With no annotations, the description says the tool is deterministic, fixture-verified, free for guests but rate-limited, and that supplying an api_key upgrades to the member budget. It also notes the result includes a Guild-signed provenance envelope, which is useful behavioral context.

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 repeats 'deterministic' and the unit dimension list across the first three sentences, making it less concise than necessary. It could be tightened without losing information.

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?

The description includes the payload schema, output schema, rate-limit/budget behavior, and provenance envelope, so a caller has enough context to invoke the tool for a simple conversion. It lacks examples and error behavior, but those are not essential for this simple tool.

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 prose and embedded payload schema explain that payload must contain numeric value and string from/to units, and the unit lists clarify accepted kinds of units. The api_key parameter is explained by the budget/rate-limit statement, though the top-level input schema itself is generic.

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 this is a deterministic unit converter that converts between units within a dimension, listing supported dimensions and example units. This distinguishes it from sibling tools like ag_calc_stats or json repair tools.

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 when to use the tool by describing unit conversion, but it does not explicitly say 'use this when...' or contrast it with alternatives. The unit dimension qualifier and examples give context, but not explicit usage direction.

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