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

Annotations already declare readOnlyHint true and destructiveHint false, so the safety profile is covered. The description adds essentially no behavioral detail beyond the Peerlytics qualifier, omitting what a lookup returns, whether it is an exact-ID fetch, or any edge behavior.

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 single sentence is brief and free of fluff, but it is so minimal that it sacrifices useful content. The description reads more like a short label than a structured tool definition.

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?

With no output schema and a large set of ambiguous sibling tools, the description should state what kind of vault data is returned and how this differs from nearby explorer and vault tools. It does neither, so the agent is under-informed for a correct call.

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?

Schema description coverage is 100%, with 'id' described as 'Vault ID' and params explained as raw JSON merged beneath typed fields. The description does not need to compensate, so the schema-heavy baseline of 3 is appropriate.

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 states a clear verb ('Look up') and resource ('a vault on Peerlytics'), so an agent knows it is a retrieval operation. However, it does not differentiate this tool from closely named siblings like peer_vault_show or peer_market_vaults, so it falls short of a 5.

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?

No guidance is given about when to use this tool instead of the many sibling vault/explorer tools in the same list. There is no mention of alternatives, prerequisites, or the typical scenario for a vault lookup, leaving the agent to infer selection from the name alone.

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