wallet_send_transaction

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

With no annotations, the description carries the full behavioral burden. It does disclose one meaningful trait — missing gas/nonce values are auto-filled via an RPC call — but omits that the operation is irreversible once broadcast, that it consumes gas, and that the password decrypts a private key held locally.

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 compact sentences, zero filler, with the core action stated first and the auto-fill behavior second. Nothing needs to be cut.

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?

For a signing-and-broadcasting tool with a nested transaction object, no annotations, and no output schema, the definition leaves real gaps: what is returned (a tx hash?), failure behavior, and network/chain assumptions. The nested EVM/SVM transaction fields are covered by the schema, which helps.

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 description coverage is 100%, so the baseline is 3. The phrase 'fills in missing gas/nonce params' adds a little meaning by signaling those transaction fields are optional to supply, but it adds nothing about password or walletId beyond the schema.

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 compound verb and resource: 'Sign and broadcast a transaction.' The combination of signing plus broadcasting implicitly distinguishes it from wallet_sign_transaction, which by name only signs, but the description never names that sibling to make the boundary explicit.

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 only implied: an agent can infer this is the tool for submitting a transaction to the network. There is no explicit statement of when to prefer it over wallet_sign_transaction, nor any prerequisites (funded wallet, unlocked keystore, correct chain).

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