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 does well by stating this is a quote-only operation ('No transaction is built') and listing what the return includes. However, it doesn't mention rate limits, authentication requirements, error conditions, or what happens if the quote fails - important behavioral aspects for a quote tool.

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 front-loaded with the core purpose in the first clause, followed by return details and a crucial behavioral note. Every sentence earns its place - the first states what it does, the second explains returns, and the third clarifies what it doesn't do. No 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 9-parameter tool with no annotations and no output schema, the description provides adequate but incomplete context. It explains the tool's purpose and return format well, but doesn't cover error handling, rate limits, or provide guidance on parameter interactions. Given the complexity and lack of structured metadata, more behavioral context would be helpful.

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 only 44% schema description coverage, the description adds significant value by explaining the tool's dual purpose (swap vs bridge) which helps understand the fromChain/toChain parameters. However, it doesn't provide additional context about specific parameters like wallet format, token address patterns, or the relationship between slippage parameters that would fully compensate for the schema coverage gap.

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 tool's purpose with specific verbs ('Get a LiFi aggregator quote') and resources ('token swap or bridge'), distinguishing it from all sibling tools which focus on positions, transactions, or other DeFi operations rather than quote aggregation. It explicitly mentions both same-chain swaps and cross-chain bridges.

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 a token swap or bridge') and distinguishes it from transaction execution tools by stating 'No transaction is built.' 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.