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

With no annotations, the description carries the full burden and does disclose meaningful behavior: frozen deposits affect credited/owed shares, pending requests have cohort epochs and cutoffs, and requests are never instant. It stops short of explicitly stating read-only safety, permissions, or error behavior, but the lifecycle context is substantial.

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 front-loaded with the tool's purpose and then adds the lifecycle context in a second sentence. It is dense but appropriately sized for the complexity, though the first sentence is a long field list rather than tightly structured prose.

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 no output schema, the description does a good job enumerating what the status returns and explaining the epoch/claim lifecycle. The main remaining gap is the account parameter format, plus no explicit note about permissions or invalid-account behavior.

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 single account parameter has 0% schema description coverage, so the description should compensate. It identifies the account as the subject whose standing is returned, but does not specify expected format (address, ID, etc.) or constraints.

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 that the tool returns an account's standing in every fund and names the key status fields it covers, so the resource and scope are clear. It does not explicitly distinguish itself from sibling quote tools such as vault_claim_quote or vault_deposit_quote, which keeps it from 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?

The description implies usage by explaining the request -> freeze/settlement -> claim cycle and the possible next steps (wait / claim / redeem). However, it never explicitly says when to call this instead of the quote or action tools, leaving alternatives to inference.

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