hedera_freeze_token_account

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

No annotations are provided, so the description must convey behavioral traits. It states the tool builds an unsigned transaction and blocks transfers, but omits important details: whether it requires a freeze key, whether the account must already be associated, and what happens to existing allowances or scheduled transactions.

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 is very concise (one sentence), which aids readability. However, it is too brief for a tool that performs a sensitive financial operation. The 'Build (unsigned)' qualifier is front-loaded, but overall structure lacks sufficient detail.

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 no output schema and no annotations, the description should provide more context about what the tool returns, what inputs are needed beyond the basics, and any side effects. It does not mention that the transaction needs to be signed and submitted, nor any restrictions on when freezing is allowed.

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 input schema has 3 parameters with 0% description coverage. The parameter names ('tokenId', 'accountId', 'payerAccountId') are self-explanatory, but the description adds no detail about their format, purpose, or constraints (e.g., tokenId in '0.0.x' format). The optional 'payerAccountId' is not explained.

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 action ('Freeze an account for a token') and the effect ('blocks transfers'). It distinguishes itself from sibling tools like hedera_unfreeze_token_account and hedera_pause_token by specifying the freeze action.

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 guidance on when to use this tool vs alternatives (e.g., pausing, wiping). No mention of prerequisites like token association, KYC, or key requirements. The term 'Build (unsigned)' hints at usage context but lacks actionable instructions.

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