prepare_tron_vote

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

Annotations already indicate destructive and idempotent behavior. The description adds that the transaction replaces votes atomically, returns a preview and opaque handle, and is for Ledger USB-HID signing. No contradiction with annotations.

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 dense paragraphs with front-loaded purpose, followed by behavioral details, preconditions, and return value. Every sentence adds value; no waste.

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?

No output schema, but description explains return value (preview + handle) and how to proceed (send_transaction). References sibling tool for preconditions. Covers all necessary context for correct usage.

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% with descriptions for both parameters, but the description adds extra context: the atomic replacement, the need to pass full allocation, empty array clearing, the count unit (1 vote = 1 TRX), and the sum constraint relative to available TRON Power.

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 that the tool builds an unsigned TRON VoteWitnessContract transaction to cast votes for Super Representatives, distinguishing it from siblings like prepare_tron_freeze or prepare_tron_claim_rewards.

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?

Explicitly says the vote replaces all prior votes atomically, to pass every SR intended, that an empty array clears votes, and to check available TRON Power via list_tron_witnesses. Also mentions reward harvesting via prepare_tron_claim_rewards.

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