xah_amount

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

The description discloses the offline nature and the conversion rate. Since no annotations are provided, the description carries full burden. No side effects or errors are mentioned, but for a local conversion, this is sufficient.

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?

Two sentences with no wasted words. The purpose and key detail (conversion rate) are front-loaded. Extremely concise.

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 tool is simple with 2 parameters and no output schema. The description covers the conversion purpose, the conversion factor, and offline nature. No gaps for this specific 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?

Schema coverage is 0%, but the description does not explicitly describe parameters. However, the schema provides an enum for 'from' and required fields, which are self-explanatory. The description adds the conversion context but no additional parameter semantics.

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 the tool converts between XAH and drops with the conversion rate. It distinguishes itself from sibling tools, which are various Xahau utilities unrelated to unit 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?

The description implies the usage context: use when needing to convert XAH to drops or vice versa. It explicitly says 'Offline', indicating no network call is needed. No alternatives are listed, but given the tool's simplicity, this is adequate.

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