freeze_klv

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

Description discloses that the tool builds an unsigned transaction for client-side signing, which is critical behavioral information beyond annotations. It also explains the staking and resource benefits. No contradiction with annotations.

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 efficiently convey the action, purpose, and return type without unnecessary words.

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 is complete for this straightforward tool. It covers the action, purpose, return type, and parameter context. No output schema is needed as the return is described.

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?

Input schema covers all 3 parameters with descriptions (100% coverage). Description does not add additional per-parameter semantics beyond what schema provides.

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 the tool builds an unsigned Freeze KLV transaction on the Klever blockchain. It specifies the purpose (freezing KLV for energy/bandwidth and staking rewards) and differentiates from sibling tools like send_transfer or invoke_sc.

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 explains the benefit of freezing KLV (energy/bandwidth, staking rewards), implying when to use it. However, it does not explicitly state when not to use it or provide direct alternatives.

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