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

No annotations are provided, so the description carries the disclosure burden. The 'Get' verb makes the read-only nature reasonably clear and the description enumerates returned content categories. However, it does not mention response shape, pagination, or any prerequisite/permission considerations, leaving some behavioral aspects unspecified.

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 concise sentences with no filler. The first sentence front-loads the action and resource, and the second sentence explains the lookup modes. Every clause contributes useful information.

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 no annotations, the description has to explain what the call returns, and it does so by naming risk breakdown, recent events, and historical snapshots. It does not detail exact response fields or behavior for ambiguous parameter combinations, but the essential information for using a single-vault lookup tool is present.

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 schema already provides 100% parameter coverage, so the baseline is 3. The description adds meaningful value by stating the two lookup modes — standalone 'id' OR the 'network + address' pair — which clarifies the intended parameter combination and reduces the risk of supplying contradictory parameters.

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 specific verb and resource ('Get detailed information about a specific DeFi vault') and lists the included content areas: risk breakdown, recent events, and historical snapshots. It distinguishes itself from the narrower get_vault_risk_breakdown sibling by using 'including', though it does not explicitly contrast itself with any sibling.

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 clearly implies when to use the tool: when an agent needs comprehensive details about a single vault and has either an ID or network+address. It does not name excluded cases or alternatives, but the targeted 'specific vault' framing provides clear context without misleading the agent.

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