Broadcast Transaction

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

Given no annotations, description discloses key behavior: auto energy delegation before broadcast and different modes based on authentication. However, lacks details on failure states or permissions needed.

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 sentences, front-loaded with main purpose, no extraneous information. Efficient and clear.

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?

Covers main functionality and modes but does not describe return value for authenticated broadcast (only cost estimate for unauth). With no output schema, this is a gap for completeness.

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?

Single parameter txData is well-described in schema (100% coverage). Description adds context ('pre-signed transaction with auto energy delegation') but does not significantly extend schema meaning. Baseline 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?

Description clearly states the verb 'broadcast' and resource 'pre-signed TRON transaction', and distinguishes by mentioning auto energy delegation, setting it apart from siblings like broadcast_signed_permission_tx.

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?

Explains when to use (pre-signed transaction needing delegation), authentication methods (API key or USDC), and behavior without authentication (cost estimate). Could be more explicit about alternatives but provides good context.

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