broadcast_transaction

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

The description adds no behavioral context beyond what annotations already declare (destructiveHint=true, idempotentHint=false). It does not mention that broadcasting is irreversible, requires a properly signed transaction, or what happens on network rejection. The bar is lower because annotations exist, but the description still fails to provide meaningful operational context.

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 concise sentences, front-loaded with the core action. Every word contributes meaning, and there is no redundancy or padding.

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 destructive, irreversible network operation, the description is notably sparse. It lacks information about return values, error cases, or the irreversible nature of broadcasting. With no output schema and minimal annotations, the description should compensate, but it does not.

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 the baseline is 3. The description adds marginal value by clarifying the transaction format as a 'full signed transaction JSON object', though this slightly conflicts with the schema's 'JSON string' type. No additional meaning is provided for the 'network' parameter.

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 action (broadcast) and the resource (signed transaction) to the TRON network, making the purpose unambiguous. It implies a distinction from broadcast_hex by specifying 'full signed transaction JSON object', though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like broadcast_hex or create_transaction. The description only states what it does, not the conditions or prerequisites for using it.

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