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

No annotations exist, so the description carries the full load and does substantial work: it declares 'Read-only; nothing is sent', notes NAV comes from the chain, and explains the queue behaviour (deposit queues, converts at the next epoch freeze up to a week later, redeemed in kind at a later freeze) and the deposit gate. Not a 5 because it says nothing about result size, pagination, or how many vaults come back.

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?

Front-loaded with the resource and its return contents, then the deposit/redeem timing model, then the explicit alternative. Dense but every clause adds information an agent would otherwise have to discover by calling the tool.

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?

There is no output schema, so the description must describe the payload — and it does, naming the per-vault fields and the epoch sub-structure. Combined with the read-only declaration and the timing model, an agent has everything needed to call this and interpret the result.

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 tool takes zero parameters and the schema is correspondingly empty, so there is nothing parameter-level for the description to compensate for. Baseline 4 applies; the field list in the description describes the response, not arguments.

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?

States a specific verb (list) and resource (OptionVault v2 funds) and enumerates exactly what is returned: stock token, deposit cap/room, shares, NAV, epoch phase and deposit gate. What keeps it from a 5 is that it never separates itself from the close sibling vault_status, which by name also sounds like it reports vault state — an agent cannot tell from this text which one to call.

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 'passive weekly premium income held for weeks, not a trade ... use the options market for exposure you open and close in seconds' line gives a genuine when-not, but it distinguishes the vault product from options trading rather than this tool from its siblings (vault_status, vault_deposit_quote, vault_redeem_quote). Whether to call list_vaults first for discovery, or vault_status for a single vault, is left to inference.

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