Preflight SafeSwap

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

With no annotations, the description carries the full burden and largely meets it: it discloses read-only behavior, that the transaction is never signed, that it simulates effects and compares them to intent/policy, and that it emits a signed verification receipt. Missing are prerequisites such as RPC/auth requirements, latency, or what happens on a malformed transaction.

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?

Three tightly packed sentences with zero waste; the read-only safety property and the core comparison are front-loaded, and the return values are stated last where they belong.

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?

There is no output schema, so the description correctly spends its last sentence enumerating the return values (PASS/FAIL/REVIEW plus a signed receipt), which is exactly what an agent needs. It stops short of describing error paths or verdict semantics, but for a 3-parameter tool it is otherwise complete.

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 100%, so the schema already documents all three parameters including nested intent and policy fields. The description only gestures at 'declared intent and principal policy' without expanding on the nested structures or the base64 encoding contract, so it adds little beyond the schema — the baseline of 3 applies.

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?

States a specific verb (compare simulated effects against declared intent and policy) and a specific resource (an unsigned Solana transaction), plus the tool's nature as a read-only financial-action firewall. An agent can immediately tell this is a pre-submission safety check rather than a signing or submission tool.

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?

Usage is implied by the name and the 'preflight' framing — run it on an unsigned transaction before signing — but the description never states when to call it, when not to, or what the caller should do with each verdict. With no siblings there is no alternative to route away from, so no explicit contrast is possible, but the trigger conditions remain implicit.

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