hedera_pause_token

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

The description says 'Build (unsigned)' implying it returns an unsigned transaction, not executing it. With no annotations, this is minimal behavioral disclosure. No mention of required permissions, side effects, or return type. Does not contradict annotations (none provided).

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?

Extremely short (one sentence) but omits critical information like parameter explanations and return value. Conciseness is achieved at the cost of helpfulness.

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 builds an unsigned transaction (no output schema), the description should explain the return format, how to use the result, and token requirements. It is severely incomplete for an agent to correctly invoke and process the output.

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 descriptions cover 0% of parameters. The description adds no meaning for tokenId or payerAccountId—no format, purpose, or examples. Tool completely relies on developer to infer parameter semantics from context.

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 builds a token pause transaction that halts all transfers. It distinguishes from the sibling hedera_unpause_token by specifying 'pause' vs unpause. However, 'Build (unsigned)' is ambiguous about the output format.

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 versus alternatives like freeze_token_account. No prerequisites (e.g., token must be unpaused) or when not to use it. The description lacks any usage advice.

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