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's a simulation (no transaction sent), specifies what gets returned (projected health factor and collateral/debt totals), and implies read-only nature. It doesn't mention rate limits, authentication needs, or error conditions, but covers the essential safety profile adequately.

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 concise with two sentences that front-load the core purpose and follow with critical behavioral information. Every word earns its place, with no redundancy or unnecessary elaboration.

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 financial position simulation with 5 parameters, no annotations, and no output schema, the description is reasonably complete about what the tool does and its safety profile. However, it lacks details about return format, error conditions, and doesn't fully compensate for the 0% schema coverage, leaving some gaps in understanding.

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 0% schema description coverage for 5 parameters, the description adds some value by implying the purpose of 'action' and 'amountUsd' parameters through the mention of 'adding or removing collateral, or borrowing/repaying debt.' However, it doesn't explain the semantics of 'wallet,' 'chain,' or 'asset' parameters, leaving significant gaps in parameter understanding.

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 verb ('simulate the effect') and resource ('an Aave V3 position'), with precise actions (adding/removing collateral, borrowing/repaying debt) and distinguishes from siblings by focusing on simulation rather than actual transaction preparation or execution.

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 ('to simulate the effect... on an Aave V3 position') and explicitly states 'No transaction is sent,' distinguishing it from prepare_* siblings. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the many sibling tools.

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