vaultpilot-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly explains the tool's behavior: it's a read-only simulation that doesn't sign or broadcast, returns specific result structure, has state-dependent considerations, and includes important caveats about approval timing and misleading revert reasons.

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 appropriately sized and front-loaded with the core purpose. Every sentence adds value, though it could be slightly more structured with clearer separation between usage guidelines and caveats. The information density is high without 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 complex transaction simulation tool with no annotations and no output schema, the description provides comprehensive context. It explains the tool's purpose, when to use it, behavioral characteristics, parameter considerations, and important limitations. This adequately compensates for the lack of structured metadata.

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 60% schema description coverage, the description adds meaningful context beyond the schema. It explains when to include the 'from' parameter for state-dependent calls and provides practical examples (WETH deposit, ERC-20 transfer). However, it doesn't cover all parameters comprehensively, particularly the 'chain' parameter which has an enum but no semantic explanation in the description.

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 ('Run an eth_call against the chain's RPC to simulate a transaction without signing or broadcasting it') and distinguishes it from siblings like prepare_* and send_transaction tools. It explicitly mentions the verb 'simulate' and resource 'transaction' with clear scope.

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 ('Use this BEFORE prepare_*/send_transaction to verify a contract call does what you expect') and when not to use it ('NEVER call this on a tx that depends on an approval you just submitted but haven't yet waited on'). It also mentions alternatives like automatic re-simulation at send_transaction time.

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