pair_ledger_live

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

Discloses that the session persists for future transactions, adding context beyond annotations (idempotentHint, destructiveHint). 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?

Three sentences, front-loaded with the core purpose. No unnecessary words. Every sentence adds value.

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 simple pairing tool with no parameters and no output schema, the description covers purpose, output, usage constraints, and persistence behavior. Fully sufficient.

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?

The input schema has zero parameters with 100% coverage, so the description compensates by explaining the output (URI + QR code) and the purpose. No parameter documentation needed.

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?

Clearly states the action (initiate a WalletConnect v2 pairing session), the target (Ledger Live), and the output (URI and ASCII QR code). Distinct from sibling tools like 'pair_ledger_tron'.

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 specifies 'EVM chains only' and directs to a sibling tool for TRON ('use pair_ledger_tron instead'). Provides clear when-to-use and when-not-to-use guidance.

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