vaultpilot-mcp

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it reads the device address at a specific derivation path, caches it for `get_ledger_status`, allows multiple calls to pair additional accounts with caching behavior, and returns actionable errors if requirements aren't met. It doesn't mention rate limits or authentication needs beyond the physical device requirements.

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?

The description is efficiently structured with zero wasted sentences. It front-loads the core purpose, then lists requirements, explains technical constraints, describes the caching behavior, and provides clear usage instructions. Every sentence serves a distinct purpose in helping the agent understand and use the tool correctly.

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?

Given the complexity of hardware wallet integration and no output schema, the description provides substantial context about requirements, behavior, and usage sequencing. It covers the key aspects needed for successful tool invocation but doesn't describe the return format or error response structure in detail, which would be helpful given the absence of an 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?

With 100% schema description coverage, the baseline is 3. The description adds meaningful context beyond the schema by explaining that '0 = first account, 1 = second, etc. — same convention Ledger Live uses' and clarifying the caching behavior when calling multiple times with different indices. However, it doesn't provide additional format or validation details beyond what's in the schema.

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 specific action ('Pair the host's directly-connected Ledger device for TRON signing') and distinguishes it from sibling tools like 'pair_ledger_live' by specifying it's for TRON signing via USB HID rather than WalletConnect. It explicitly mentions the resource (Ledger device) and the purpose (TRON signing).

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?

The description provides explicit guidance on when to use this tool ('Call this once per session (per account) before calling any `prepare_tron_*` tool or `send_transaction` with a TRON handle'), when not to use it (if using WalletConnect relay), and alternatives (multiple calls with different accountIndex values). It also specifies prerequisites like device being plugged in, unlocked, and TRON app open.

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