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 does an excellent job disclosing behavioral traits. It explains the transaction sweeps all eligible slices in one call, mentions the 14-day cooldown requirement, warns about potential errors when no slices are ready, describes the return format ('preview + opaque handle'), and specifies the signing method ('USB-HID signing on the paired Ledger'). The only minor gap is lack of explicit rate limit or permission 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 perfectly structured and concise. The first sentence establishes the core purpose, the second explains the sweeping behavior and lack of amount parameter, the third provides crucial prerequisite checking, and the fourth specifies the output and next steps. Every sentence earns its place with zero wasted words.

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 transaction preparation tool with no annotations and no output schema, the description provides excellent context. It explains the operation's scope, prerequisites, error conditions, return format, and next steps. The only minor gap is that without an output schema, more detail about the 'preview' structure would be helpful, though the description adequately covers the essential workflow.

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 by explaining that the 'from' parameter represents the 'owner address' that sweeps all unfreezes whose cooldown has elapsed, and references the `pendingUnfreezes[].unlockAt` field from `get_tron_staking`. This provides valuable semantic context beyond the schema's pattern validation.

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 ('Build an unsigned TRON WithdrawExpireUnfreeze transaction'), the resource ('sweeps every matured unfreeze slice'), and distinguishes it from siblings by focusing on TRON-specific unfreeze expiration. It explicitly mentions the lack of amount parameter, which differentiates it from other prepare_* tools that require amounts.

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 ('if every entry's `unlockAt` is still in the future, TronGrid returns 'no expire unfreeze' and this tool errors') and directs users to inspect `pendingUnfreezes` from `get_tron_staking` first. It also specifies the next step ('forward via `send_transaction` for USB-HID signing').

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