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 well by disclosing key behavioral traits: it builds an unsigned transaction (not executed), includes conditional approval logic, explains the 'max' amount feature, and mentions on-chain resolution of base token. It doesn't cover rate limits, gas estimation, or error conditions, but provides substantial operational context.

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 extremely concise (two sentences) with zero wasted words. It front-loads the core purpose and follows with important operational details. Every sentence earns its place by providing critical information about transaction building and parameter usage.

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 5 parameters, no annotations, and no output schema, the description is adequate but has gaps. It covers the core purpose and some behavioral aspects but doesn't explain what the output looks like (unsigned transaction data format), error conditions, or integration with sibling tools like send_transaction. Given the complexity, it should provide more complete operational context.

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?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds some value by explaining the 'amount' parameter's 'max' special value and the approvalCap behavior, but doesn't provide additional semantic context beyond what's already in the schema descriptions for wallet, chain, and market parameters.

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 Compound V3 repay transaction — encoded as supply(baseToken) against an outstanding borrow.' It distinguishes from siblings like prepare_compound_borrow and prepare_compound_supply by focusing on repay functionality, and includes the technical detail about encoding as supply.

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 clear context for when to use this tool (for Compound V3 repay transactions) and mentions the 'max' amount feature. However, it doesn't explicitly contrast with alternatives like prepare_aave_repay or prepare_morpho_repay, nor does it specify when NOT to use it (e.g., for partial vs full repay scenarios beyond the 'max' hint).

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