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

Annotations indicate destructiveHint=true, and the description confirms a write operation ('Broadcasts'). It adds value by specifying the return fields (transaction hash, block number, gas used) and the required signing method. It does not mention cost or failure modes, but the annotation covers the essential behavioral trait.

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?

The description is only two sentences: the first states purpose and required input format, the second states return values. Every sentence is necessary, and the structure is front-loaded, allowing quick comprehension.

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 two required params and no output schema, the description covers the return values and input format thoroughly. It lacks details on error handling or gas implications, but given the destructive annotation and typical Ethereum transaction semantics, it is sufficiently complete for an AI agent.

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 baseline is 3. The description adds extra context beyond the schema by explaining the signedTransaction format with an example (ethers wallet.signTransaction(tx)) and detailing the configId format. This enhances understanding for an agent selecting the tool.

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 clearly states the verb 'Broadcasts' and the resource 'signed raw Ethereum transaction'. It distinguishes from sibling tools like send_meta_transaction by specifying that the transaction must come from local wallet signing, making the purpose unambiguous.

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?

The description gives clear guidance on when to use this tool: 'signedTransaction must be 0x-prefixed RLP-encoded hex obtained from local wallet signing'. It also mentions the configId parameter format. However, it does not explicitly exclude scenarios (e.g., when using meta-transactions) or provide alternatives, which would improve guidance.

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