Request EVM transaction approval

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

The description adds valuable behavioral context beyond annotations: it states the tool simulates before queueing, never claims signature before approval, and enforces asciiExplanation constraints. This complements the annotations (readOnlyHint=false, openWorldHint=true) without contradicting them.

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 compact at two sentences, front-loads the core function, and adds a critical safety caveat and a mandatory parameter rule without wasted 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 covers the primary action and key safety detail, but doesn't explain the sign vs sign-and-submit modes, return values, or lifecycle of the queued request. Given the absence of an output schema and presence of a nested transaction object, additional context would help the agent use the tool correctly.

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?

Only asciiExplanation receives enhanced semantic guidance in the description, restating and expanding on the schema's requirement. The many other parameters (mode, chainId, transaction fields) are left to the schema, which is sparse given only 13% schema description coverage; the description could have compensated more.

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 opens with 'Simulate and queue an EVM transaction for explicit browser-wallet approval,' which clearly identifies the action (simulate/queue) and resource (EVM transaction) and distinguishes it from sibling tools like request_solana_transaction or list_transaction_requests. The additional caveat about not claiming signature reinforces the tool's role.

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 tool should be used when an EVM transaction needs user approval, and the name/description differentiate it from Solana/Sui variants. However, it does not explicitly state when to use this over the get/list/cancel transaction request tools, nor does it describe prerequisites or exclusions.

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