Fetch Solana Vaults

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

With no annotations, the description carries the full burden. It does disclose that results include basic vault information and transactional identifiers, which is useful for downstream operations. However, it does not explicitly state read-only behavior, pagination, or that the default limit of 6 means it does not fetch 'all' unless the limit is increased.

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 two short sentences with no filler. The hint sentence provides valuable output context, and the structure is front-loaded with the core purpose.

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?

The tool is simple, but without an output schema, the description should fully explain the return format. It gives examples of fields but not a complete list, and it does not address the default limit or behavior when no limit is specified. It is adequate for a basic fetch tool but leaves gaps.

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 fully documents the single 'limit' parameter with a clear description and default. The tool description adds no parameter-specific meaning beyond the schema, 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 uses a specific verb ('Fetch/Search') and clearly identifies the resource ('all available vaults from across *Solana/SVM-chain*'). This distinguishes it from EVM and Sui siblings and from action-oriented tools like deposit/withdraw. The hint about result contents reinforces the tool's purpose.

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 implies usage for Solana/SVM vault fetching via the chain qualifier, but it does not provide explicit when-to-use guidance or mention alternatives like fetch-vault-analytics. There are no exclusions or complementary tool references.

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