Prepare the simulated wallet transaction

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

Adds context beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by detailing that the server does not sign/submit and rejects caller-provided data. 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 concise sentences, front-loaded with the primary action, no 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?

Given low complexity (1 param, no nested objects) and the presence of an output schema, the description fully covers the tool's behavior for an AI agent to decide and invoke 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 parameter is planHash, but the description does not explain its purpose or format beyond the schema pattern. With 0% schema description coverage, the description should provide meaning, but it only says 'latest non-expired simulation' without linking to the parameter.

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?

Clearly states the tool returns the exact unsigned transaction from the latest non-expired simulation. Distinguishes from sibling tools like plan_simulate by specifying output nature and constraints.

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?

Explicitly says the server does not sign or submit the transaction and never accepts caller-provided targets or calldata, implying it is for retrieval only after simulation. Could be more explicit about alternatives, but the context from sibling tools makes it clear.

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