vaultpilot-mcp

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

With no annotations provided, the description carries full burden and delivers comprehensive behavioral disclosure. It explains security implications (self-reported wallet/peerUrl, need for user confirmation), cache behavior (tron array read from cache populated by pair_ledger_tron), and operational details (send_transaction re-probes USB for TRON).

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?

While information-rich, the description is lengthy (over 200 words) with multiple complex sentences. It could be more front-loaded; the core purpose appears early, but security details and usage examples extend it significantly. Every sentence adds value, but tighter structuring would improve readability.

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 tool's complexity (wallet connectivity with security implications), no annotations, and no output schema, the description provides exceptional completeness. It explains return values (accounts array, tron array with structure), security protocols, when to use it, and integration with other tools like pair_ledger_tron and send_transaction.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters but focuses on the tool's purpose and usage context, which is correct for a parameterless tool.

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 the tool's purpose: to report WalletConnect session status for EVM chains and cached TRON Ledger pairings. It distinguishes itself from siblings by focusing on wallet connectivity status rather than portfolio data, transactions, or pairing actions, with specific mention of sibling tool '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?

The description provides explicit usage instructions: 'Call this FIRST whenever the user refers to their wallet(s) by position or nickname instead of by address' and lists specific examples. It also includes exclusion guidance: 'Do NOT ask the user to paste an address if it's already in accounts or a tron[*].address here.'

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