Fetch Vault Analytics

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

Annotations are empty, so the description bears full responsibility for behavioral disclosure. It makes clear this is a read-only fetch operation and mentions APY as included data, but it does not disclose return structure, potential errors, or whether any filters or pagination exist. This is adequate but not deeply informative.

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 compact and front-loaded, with the core purpose in the first sentence. The instructions are direct and actionable, adding value without redundancy. Every sentence earns its place.

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 tool's simplicity (2 params, no output schema, no annotations), the description is largely complete: it defines the purpose, gives usage guidance, and the schema covers parameter details. It could be improved by describing the output format, but the missing detail is not critical for basic invocation.

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?

The input schema covers 100% of parameters with detailed descriptions, including the array format for vaultIds and the system nature of requestId. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 'Fetch detailed analytics data for vaults' with a specific focus on 'core vault performance data such as APY.' This distinguishes it from sibling tools like solana-fetch-vaults or evm-fetch-vaults, which are likely focused on retrieving vault lists rather than analytics.

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 usage context: 'Use this tool before making any asset optimization decisions' and 'Use this tool when rebalance/compare/analyze vaults.' This gives clear when-to-use guidance, though it does not mention when not to use it or name alternatives.

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