pair_ledger_tron

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

Annotations already indicate idempotentHint=true; description adds specifics about caching, BIP path, error behavior, and per-session requirement. No contradictions 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?

Clear, well-structured description with a lead sentence then bullet-style breakdown of requirements, technical context, parameter usage, and error handling. No redundancy.

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?

Thoroughly covers prerequisites, behavior, parameter usage, and relation to sibling tools (get_ledger_status, prepare_tron_*). Appropriate for a pairing tool with no output schema.

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?

Input schema covers accountIndex with 100% coverage; description enriches with context about BIP path, default, and multi-call behavior for additional accounts.

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 explicitly states 'Pair the host's directly-connected Ledger device for TRON signing' using a specific verb and resource, clearly distinguishing it from other pair_ledger_* siblings by specifying TRON and USB HID.

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?

Provides explicit requirements (USB connection, device unlocked, Tron app open), context for TRON vs WalletConnect, and sequencing instructions (call before prepare_tron_* tools and send_transaction). Lacks explicit 'when not to use' but strongly implies alternatives via sibling names.

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