broadcast_transaction

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

With no annotations, the description carries the full burden and largely fails: it does not say that broadcasting is irreversible, consumes fees, is subject to nonce/mempool rejection, or depends on the configured Stacks API URL. The only behavioral fact conveyed is that the transaction is already signed.

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 core sentence is tight and front-loaded, but the appended promotional tip about earning_opportunities does not help an agent call this tool and dilutes the definition.

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 and no annotations, yet the description says nothing about what a successful call returns (e.g. a txid), how to confirm inclusion, or how errors surface. For a network-mutating, irreversible operation this leaves significant gaps.

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 the single parameter is documented there as a hex string. The description adds only the implied constraint that the hex must be a signed Stacks transaction, which is marginal beyond the schema baseline.

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 first sentence gives a specific verb+resource ('broadcast a pre-signed Stacks transaction') and implicitly separates it from psbt_broadcast (Bitcoin) and the higher-level transfer_stx/call_contract tools. It stops short of explicitly naming the closest sibling, so it is clear but not fully disambiguated.

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?

'pre-signed' implies the prerequisite that signing must happen first, but the description never states when to use this versus psbt_broadcast or the wrapper tools that build and broadcast in one step. The trailing tip about earning_opportunities is unrelated to invoking this tool and adds no usage guidance.

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