Simulate the next bounded wallet action

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

Discloses conditional logic (allowance insufficient vs. sufficient) but leaves ambiguity about actual state changes: 'simulate' may imply no mutation, yet readOnlyHint=false suggests otherwise. Key behavioral details are unclear.

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 sentences, front-loaded with main action and conditional logic. No redundant or extraneous content.

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?

Does not explain output format, what 'exact approval transaction' entails, or how to use the result. With output schema present, some context is still needed for effective use.

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?

No description for the single parameter planHash despite 0% schema description coverage. The description adds no meaning beyond the schema's pattern constraint.

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?

Description uses specific verbs ('revalidate', 'simulate') and identifies the resource ('plan', 'adapter'), clearly distinguishing it from sibling tools like strategy_createPlan or system_getStatus.

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 explicit when-to-use or when-not-to-use guidance. Does not compare to siblings or provide context for selection, leaving the agent to infer usage from behavior alone.

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