Send Transaction

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the call only 'starts' a request and requires 'user approval' (implying an async, human-gated flow), but it does not say what happens after starting, whether anything is irreversible, what auth/permissions are needed, or how the request is later resolved.

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?

A single front-loaded sentence with no filler, and the approval/transport information arrives immediately. It is appropriately sized for what it attempts, though the brevity contributes to the coverage gaps elsewhere.

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 7-parameter transaction-submitting tool with no annotations and no output schema, the description is too thin. It omits the approval lifecycle (e.g., that status is later checked via get_request_status), the difference between execution profiles, and any routing guidance among the many send_* and sign siblings.

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 86%, so the property descriptions already document to/data/from/chain/value/profileId/executionProfile. The prose adds only the framing of a single transaction and the WalletChan RPC route, so the baseline of 3 is appropriate.

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?

The description names a specific verb ('Start'), the underlying resource ('eth_sendTransaction request'), and the transport ('WalletChan RPC'), and the word 'single' hints at the distinction from the batch-oriented send_calls / send_prepared_calls siblings. It stops short of explicitly naming an alternative, so an agent must infer the contrast.

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?

There is no when-to-use or when-not-to-use guidance. With siblings like send_calls, send_prepared_calls, agent_eoa_send_transaction, and agent_oneshot_relay_calls all capable of sending transactions, the description never says which path to pick or what prerequisites apply.

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