Request Sui transaction approval

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

The description adds behavioral context beyond annotations by noting the tool simulates and queues transactions rather than immediately submitting them. The mandatory asciiExplanation requirement is also disclosed, which is a non-obvious behavioral constraint.

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 two sentences long, immediately stating the purpose and then highlighting the most critical input constraint. No wasted words, with essential information front-loaded.

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 omits important context about the transaction approval lifecycle, such as how a queued request is later retrieved or canceled, and does not explain the difference between 'sign' and 'sign-and-submit' modes. Given the presence of sibling tools for these operations, more guidance is needed.

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 only 29%, but the description adds meaning to key parameters: transactionBase64 is described as serialized Sui TransactionData, and asciiExplanation is described as ASCII-only and required. Other parameters (mode, network, expectedSigner, expiresInMinutes) rely on schema enums and are left unexplained.

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 simulates and queues serialized Sui TransactionData for explicit approval, specifying the exact resource (Sui) and action (simulate/queue). This distinguishes it from sibling tools for EVM and Solana transactions.

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 this is the tool for Sui transactions via the explicit 'Sui Wallet Standard extension' and 'serialized Sui TransactionData'. However, it does not explicitly mention when to prefer this over the EVM/Solana request tools or cancellation/retrieval tools.

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