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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the returned transaction is unsigned, uses a confirmed/fresh blockhash, and must be signed and sent in the same turn because reuse of stale output is invalid. It does not spell out the auth requirement or any rate limits, but the mcp_token 403 condition is already documented in the schema.

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 tight sentences, front-loaded with the scope constraint and purpose, then the workflow ordering, then the anti-pattern. No filler and nothing that duplicates structured fields.

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?

With no output schema, the description does the work of defining the artifact ('fresh unsigned SOL transfer') and the mandatory follow-on chain, which is the key completeness need for a build-and-sign pipeline tool. The one remaining gap is the exact shape of the returned unsigned payload (fields, serialization), which the agent must infer.

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% and every parameter (to, from, amount, mcp_token, priority_fee_micro_lamports) is documented with format, base58, units, and a retry hint. The description adds no parameter-level detail; the 'fresh blockhash' mentioned is not a caller-supplied argument. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('build') and resource ('unsigned SOL transfer') with scope qualifier 'Solana native only'. It explicitly names the sibling tools it chains with (dex_wallet_sign_transaction, dex_tx_send_raw_transaction) and the one it must NOT reuse (dex_tx_transfer_preview), so an agent can distinguish it without opening a schema.

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?

Gives an explicit precondition ('Call only after the user confirms'), a required follow-up sequence ('then dex_wallet_sign_transaction and dex_tx_send_raw_transaction in the same turn'), and a prohibition ('Do not reuse dex_tx_transfer_preview output'). When-to-use, what-to-do-next, and the alternative to avoid are all stated.

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